Odd scripting problem: Conclusions at the end of a day...

Mon Mar 14 01:41:37 EDT 2016

James,

Thank you for your email.

RE: “...I only suggest the new format because it’s so much easier to read in a script, you can tell immediately what you’re looking at. “

I agree. I even went further and discovered it accepts seconds to include in the algorithm. Perhaps you’ll tell me this isn’t necessary as that is what it would do anyway, and although works, consumes unnecessary cycles?

if (current date) ≤ date ("11:59:59am") then
if (current date) ≥ date ("12:00:00Pm") and (current date) ≤ date ("4:59:59Pm") then
and 	if (current date) ≥ date ("5:00:00pm") and (current date) ≤ date ("11:59:59pm") then

RE: "None of that has anything to do with any changes in XTension at all. It’s all changes or additions (or just me learning things that AppleScript did all along) to what applescript does in the system.”

Dang… you mean you’re a Newby too! :-) 

Seriously, somehow today it was made blatantly clear to me that the time commands in XTension had changed, not AppleScript, and that I was not even using the old commands correctly. I knew better, of course, because there would be any number of things around here that would have gone haywire at the moment of installation, and I’d be on this List pronto.

RE: "I have experimented with this here, and as far as I can see the handler button works as least as well as it ever has. It doesn’t enable for new scripts at all, though I could enable it once you’ve done a check syntax for a script and I’ll add that to my list. At the moment it should enable once a script has been saved and is opened for editing.”

What I think we have here is a failure to communicate. :-) 

Perhaps you have this capability now hidden someplace else I haven’t discovered yet, but up until the installation of 725, I swear I used that Handler button to quickly build new scripts. In fact, your statement above blows me away when you say it is only ghosted for a new and unsaved script? That’s when I need it most, and there has to be something wrong with my install, as I just checked, and regardless of whether or not the script is saved, this button is ghosted on my system. How could that be, and how do I fix that?

RE: "You should read my release notes though ;) and if something new in there spikes some interest then update, if it fixes something that you’ve been having trouble with then update. Otherwise don’t worry.”

I do most certainly read anything you post, let alone release notes. I guess that’s why I felt comfortable telling Henk why I hadn’t upgraded XTension… if it ain’t broke, don’t fix it. :-)  That’s until I recently saw and read something you wrote, I think on your beta download page, and that was it helped you continue developing XTension by everyone updating to the current beta version. Upon reading that, I understood and proceeded to upgrade. It’s ironic as I remember you having me update to 685 last Fall when you were helping me on the geofence project, and you’ve been spitting them out in rapid fire ever since.

As Henk knows well, there are members of this list that finished their systems long ago, and barely watch their machine or XTension for many months or at all now, because it just works! Some are still running super early Michael versions of XTension on OS9 and PowerPC processors, and they write in occasionally to tell us all is still well. 

I also have to admit I have an aversion to the word Beta as I was always needing to be at the bleeding edge of something, and got stung more than I liked. So I no longer jump at updates for the sake of updates. I just upgraded to Quicken 2016 (Which so far I don’t like because of the UI) from Quicken 2003. Why, because it still works great, but I recognized that I needed to support Intuit for doing such a good job of tracking my $$$. 

One last thing, and that is XTension’s Doc is, IMHO, in need of an update. I personally would like to see a Help menu item added to XTension. I know everyone hates to write Doc, so I have an idea for you. Why not let the List help you write the individual command pages ideally rich with examples, for a sort of online dictionary of XTension’s commands.

Just sayin such a feature would really help us Newbies just like you providing .RTF in the logs.

Best wishes,

George

> On Mar 13, 2016, at 6:41 PM, James Sentman <james at sentman.com> wrote:
> 
> 
>> On Mar 13, 2016, at 6:13 PM, George Handley <ghandley at kc.rr.com <mailto:ghandley at kc.rr.com>> wrote:
>> 
>> I have used the old style syntax of the current date command in probably hundreds of scripts. I wonder why they all still seem to be working fine… probably no invisible tab... ya think? :-)
>> 
> 
> The other way of doing it is perfectly valid, I only suggest the new format because it’s so much easier to read in a script, you can tell immediately what you’re looking at. There is no reason to go back through all your old scripts and change them, do what you’re comfortable with. But being able to more easily read a script later is really important too!
> 
> None of that has anything to do with any changes in XTension at all. It’s all changes or additions (or just me learning things that AppleScript did all along) to what applescript does in the system.
> 
> 
>> Again, where can I find a document explaining all the changes or is there not one yet? I can’t find it on your website or Wiki either. I’m still trying to get that “Handlers” button working too. Is there a newer xtensionmanual.pdf than the one I use dated 12/8/2010?
> 
> I have experimented with this here, and as far as I can see the handler button works as least as well as it ever has. It doesn’t enable for new scripts at all, though I could enable it once you’ve done a check syntax for a script and I’ll add that to my list. At the moment it should enable once a script has been saved and is opened for editing. Assuming the script has any handlers to be listed there. What are you expecting it to do that it’s not doing otherwise?
> 
> 
> 
>> 
>> Henk, for the most part, all of James 42 new versions supported lots of new toys as you know, and probably play with. OTOH, for the most part, my system consists of mostly lots of plain vanilla parts with only a few bells and whistles James will tell you. Generally, I don’t upgrade any App unless I know it newly supports features I want and need, or is a bug or security fix, or required for a new OS. I’m sure James will disagree, but I basically support the KISS rule of thumb, and avoid a lot of trouble not always upgrading.
>> 
> 
> 
> 
> yes :) you generally stay with the last version I insisted you update to in order to fix some problem that is popping up. I do all these updates to make sure everyone knows that XTension is regularly updated and that we’re completely active in development. I have no interest in forcing you guys to update every week or so! You should read my release notes though ;) and if something new in there spikes some interest then update, if it fixes something that you’ve been having trouble with then update. Otherwise don’t worry.
> 
> Thanks,
>  James

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20160314/8cf1c790/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: For List 5 3-13-16.jpg
Type: image/jpeg
Size: 145568 bytes
Desc: not available
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20160314/8cf1c790/attachment.jpg>