Re: Intel UI scripting
Re: Intel UI scripting
- Subject: Re: Intel UI scripting
- From: Takaaki Naganoya <email@hidden>
- Date: Fri, 23 Jun 2006 11:01:26 +0900
- Thread-topic: Intel UI scripting
Hmm... It is deep plobrem.
I feel that there is a kind of plobrem in accessing property files in Intel
Mac environment. I faced to many crash in launching Script Editor , other
AppleScript Studio based apps and Automator.
# Already I wrote bug report and send a lot of crash log files
I think that the release date of Mac OS X 10.4.7 updater may delay due to
these kind of plobrems.
--
Takaaki Naganoya
Piyomaru Software
http://piyo.piyocast.com
--Universal Binary Application List ( gathered by "UNI_VERSAL")
http://universal.piyocast.com/A001.html
On 06.6.23 10:40 AM, "Scott Doenges" <email@hidden> wrote:
> Bill, Takaaki and Paul,
>
> Thanks for the responses and information. I was able to narrow down
> exactly what's causing this problem. It's an interesting one... it's
> not an issue with UI Browser, more likely with the Intel Finder or
> some other Intel OS framework. Here's the scoop:
>
> So the "Enable access for assistive devices" setting is toggled by
> the absence or presence of the following file: /var/
> db/.AccessibilityAPIEnabled (note the leading period - it's an
> invisible file). If you check the box, this file gets created and
> the setting is enabled; if you uncheck the box, the file gets deleted
> and the setting is disabled. One of my Applescript's first steps is
> to enable this setting on the fly using the following action:
>
> do shell script "touch -f /var/db/.AccessibilityAPIEnabled" with
> administrator privileges
>
> However the "touch" command simply creates an empty file - but if you
> go into System Prefs and check the box manually on either PPC or
> Intel OS X, then look at the contents of the .AccessibilityAPIEnabled
> file, it just contains the letter "a" followed by a carriage return.
>
> But an empty file works just as well, at least on a PPC machine - all
> applications show up normally in UI Browser, and all UI scripts work
> normally. On an Intel machine, an empty file doesn't seem to enable
> UI scripting for the Finder - as I mentioned, UI scripts work just
> fine in System Prefs, iChat and other apps, but not in the Finder.
> But if you create the empty file then go look in the Universal Access
> preferences on either PPC or Intel OS X, the "enable access" checkbox
> is checked.
>
> So evidently I need to come up with a better way to automate enabling
> this setting (I also plan on filing a bug report via ADC, just to
> make sure Apple is aware of this potential problem).
>
> Any suggestions for better methods of creating the proper file? I
> obviously can't use UI scripting to go in and check that box for
> me! :-) Does anyone have suggestions for shell commands that can
> write text into a file?
>
> thanks for your help, it's greatly appreciated!
>
> Scott
>
> On Jun 22, 2006, at 4:13 AM, Bill Cheeseman wrote:
>
>> on 2006-06-22 12:47 AM, Scott Doenges at email@hidden wrote:
>>
>>> using Prefab UI Browser (granted, not updated for over a year)
>>
>> As others have said, make sure the "Enable access for assistive
>> devices"
>> setting is turned on in System Preferences (or that "Enable GUI
>> Scripting"
>> is turned on in AppleScript Utility"). However, if it is only the
>> Finder
>> that isn't working while other target applications do work, you
>> must already
>> have done that.
>>
>> Unfortunately, I can't think of any reason why UI Browser or the
>> accessibility features of the system wouldn't work with Finder
>> while working
>> with other target apps. I have only been able to do limited testing on
>> Macintel machines, but it did work on Finder when I tried it. It
>> would be
>> helpful if you have installed Developer Tools, to run Apple's
>> Accessibility
>> Inspector utility -- it will give you a second opinion as to
>> whether the
>> Finder is accessible on your Macintel machine.
>>
>> If you find an explanation for this issue, please let me know ASAP
>> so that I
>> can deal with it for version 2.0, which is almost done. Version 2.0
>> will be
>> a universal binary; it will have several new features; and it will
>> have a
>> few bug fixes. It will become available some time this summer
>> (which gives
>> me three months minus one day to get it done).
>>
>> --
>>
>> Bill Cheeseman - email@hidden
>> Quechee Software, Quechee, Vermont, USA
>> http://www.quecheesoftware.com
>>
>> PreFab Software - http://www.prefab.com/scripting.html
>> The AppleScript Sourcebook - http://www.AppleScriptSourcebook.com
>> Vermont Recipes - http://www.stepwise.com/Articles/VermontRecipes
>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Applescript-users mailing list (Applescript-
>> email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>> 40comcast.net
>>
>> This email sent to email@hidden
>
> _______________________________________________
> 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
_______________________________________________
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