Re: Panther and AppleScript property not retained - why?
Re: Panther and AppleScript property not retained - why?
- Subject: Re: Panther and AppleScript property not retained - why?
- From: DigitEL <email@hidden>
- Date: Thu, 11 Dec 2003 00:13:27 -0800
On Dec 10, 2003, at 6:55 AM, Tero Siili wrote:
I have some pre-Panther scripts, which after upgrade to Panther seem
to have lost their ability to save/store/retain the property value
assigned during the first run after compilation; the scripts have a
branch checking whether a property is defined (at least that is the
intention) and ask for the user to define the property, if it is
initially undefined. The scripts, however, keep on asking for the
property each and every run, although the property has been defined on
previous run. An example snippet of such a script is below:
I have noted this behaviour in some scripts and folder actions and
posted awhile back about it with no response so I thought it was just
me but it does appear to coming up more often.
I wrote a column once about the various kinds of tests that you need
to do to sort out what's going on with properties storage under the
various run/save/rerun scenarios
http://maccentral.macworld.com/features/applescriptprimer49/
I have not retested Script Editor 2 for this behaviour, but it sounds
like there's reason to do so.
For me things run fine in the Script Editor but do not appear to save
to properties when run as compiled scripts or applets. This is by no
means consistent for all scripts and copying and pasting into fresh
script documents and saving does not appear to remedy the situation. I
emailed Mr Nebel directly about this but so far received no response
;-s
--
ForNow
EL
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.