Re: Executing AppleScripts from an 'AXTrustedProcess'
Re: Executing AppleScripts from an 'AXTrustedProcess'
- Subject: Re: Executing AppleScripts from an 'AXTrustedProcess'
- From: Tobias Zimmerman <email@hidden>
- Date: Wed, 4 Feb 2009 15:21:59 -0500
> From: Bill Cheeseman <email@hidden>
> The accessibility API is not a Cocoa API. It's a system API that can be used
> from within a Cocoa application, but it will require you to become
> comfortable with plain C system API's that have more in common with Carbon
> than Cocoa.
>
> Once you get it, it's perfectly easy to do. But there is a learning curve.
> There is some documentation, but it's a bit sketchy.
>
Thanks. I am aware of the distinction between accessibility and cocoa
-- sorry if I wasn't clear. I should have said "just getting started
programming on Mac OS X.
I also realized that I don't think that this will fully solve my
problem because I believe that I will still need AppleScript in some
circumstances to correctly discern what is the "front" window to be
moved. I am thinking primarily of the MS Office suite, which does
very strange things with the window server (apparently), such as
leaving its 'toolbox window' (which is really a glorified tool bar) at
level 0. The only way I have come up with to really get the correct
window of MS Word and Excel is to use AppleScript to find out what the
applications refer to as the 'active' window. Maybe that is possible
through the AX API, but probably beyond my current abilities (I'm
getting there, though).
> From: James Dempsey <email@hidden>
> If you do have a reproducible example of a leak, please file a bug at
> bugreporter.apple.com, and include all the information you have. A
> bug filed is infinitely more likely to be acted upon within Apple than
> a post to a mailing list (which may or may not be seen by the
> appropriate person to fix the issue).
>
> You need to be a member of ADC to use bugreporter, but a free online
> ADC membership is fine.
>
> bugreporter.apple.com is the best way for developers to report issues
> and enhancement requests - although it is largely one-way
> communication. You don't get any status information, but we
> definitely see them in engineering.
I banged together a test app that would run a simple script over and
over. Not only do I see the memory usage growing (although not
conclusively), the app reliably crashes midway through a run. Even
putting in a small pause between script executions I still get a crash
after about 500 (or less) iterations. I will post to bugreports -- I
realize the mailing lists aren't the appropriate vehicle for official
bug reporting.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden