Re: Accessibility / System Events changes in Tiger
Re: Accessibility / System Events changes in Tiger
- Subject: Re: Accessibility / System Events changes in Tiger
- From: Jeff Porten <email@hidden>
- Date: Tue, 16 Aug 2005 00:16:35 -0400
On Aug 8, 2005, at 11:34 PM, Scott Babcock wrote:
Has anyone noticed other changes in System Events since switching to
Tiger?
99% of my UI Scripting is for one-off projects which I'm not too
particular about running cross-platform; if it runs on my local
Tiger, no one but me will ever try to run it under Panther. This is
because typically my clients are only interested in the output of the
scripts and neither know nor care that UI Scripting is how I'm
getting a week's worth of manual labor done in a few hours.
That having been said, what I've noticed under Tiger is that UI
Scripting *works*. The script I just whipped up for TextEdit HTML
saving took me about 10 minutes with UIElementInspector and some
judicious pointing. That *never* happens. ;-) I'm much more used
to UI scripts being painful trial and error processes, and it's great
to see a few getting out the door on the first try.
I'm loathe to ship UI scripts because I hate telling my users, "by
the way, don't touch anything while it's running, or you might break
it." (Error-trapping all of the delays is bad enough; I'd rather go
swimming in salt water in a sandpaper bathing suit than error-trap
every last focused item I expect to target. [1]) My one exception is
the LBSnooze script which adds an automatic task to a Life Balance
hierarchy, and that was only because several people asked nicely for it.
But looking over that script, the only change I made for Panther
compatibility was to fix an "hours of date" I had in the Tiger
version. UI stuff was untouched -- and LB, while being wicked cool
software, is a monstrosity of nested hierarchical objects for UI
targeting.
That having been said, your post implies a much greater familiarity
with Cocoa objects than I have (I just think they go great with
milk). So I wouldn't be a bit surprised if you're working in a
slightly more tangled and spooky forest than I am.
[1] I just had a *great* idea for the next version of UI Scripting.
Are you listening, Chris?
on PEBKAC()
set keyboardInput to false
set mouseInput to false
growlnotify "Don't touch ANYTHING!"
if (keyboard input or mouse input)
growl -- literally
end if
ignoring user responses
(* UI scripting *)
end ignoring
end PEBKAC
Best,
Jeff
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden