Re: Script Menu in Tiger: non-persistent property bug?
Re: Script Menu in Tiger: non-persistent property bug?
- Subject: Re: Script Menu in Tiger: non-persistent property bug?
- From: Bill Cheeseman <email@hidden>
- Date: Sun, 07 Aug 2005 14:21:02 -0400
on 2005-08-07 11:38 AM, kai at email@hidden wrote:
> True - but only for the duration of a run. When run from SM, the
> changed property still doesn't persist from one run to the next.
There is a long-standing, confirmed bug in Cocoa's -[NSAppleScript
executeAndReturnError:] method, whereby it fails to save properties between
runs of a script. I reported it a long time ago, and then it was marked as
fixed, but I found out later that the fix was put in some other method that
has nothing to do with this one.
As a result, it remains true to this day that any Cocoa application that
executes scripts and neglects to work around this bug will suffer from this
same problem. Most Carbon applications will work correctly in this regard,
and some Cocoa applications do, as well -- for example, my PreFab UI
Actions.
--
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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden