"Lost script" bug confirmed by Apple
"Lost script" bug confirmed by Apple
- Subject: "Lost script" bug confirmed by Apple
- From: Paul Berkowitz <email@hidden>
- Date: Fri, 18 Apr 2003 12:34:40 -0700
I've received a confirmation via "Radar" that the serious bug I reported
earlier - the one that saves the wrong script into an applet when it quits -
is a bug with 'store script': it doesn't close the stored script's resource
fork as it should, so the calling script can get stored in it by mistake.
I don't understand why it happens just with the two circumstances I
discovered - 1) a quit handler in the calling script or 2) two very large
loaded scripts, one of which is stored - but I suppose it doesn't matter in
the end as long as the root cause is fixed. In the meantime, there doesn't
seem to be any workaround: my device for case 2 - setting each loaded script
in a handler and/or resetting it to null - doesn't help, in the 10% or so of
cases where the bug hits. In case 1, it's closer to 100% (and _is_ 100% if
there's a call to the Finder in the quit handler.) So don't store script
from a calling script with a quit handler. I don't know what to do about
loading long scripts until the bug is fixed.
--
Paul Berkowitz
_______________________________________________
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.