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: kai <email@hidden>
- Date: Mon, 8 Aug 2005 00:38:14 +0100
On 7 Aug 2005, at 19:24, deivy petrescu wrote:
On Aug 7, 2005, at 12:33, kai wrote:
On 7 Aug 2005, at 16:55, deivy petrescu wrote:
Are you sure you did not recompile the script?
Quite sure, Deivy - and I've just rerun the whole shooting match
again, just to be doubly confident.
I can obviously continue the sequence from SM by changing the last
line from "if n < 4 then n" to "if n > 4 then n" - but then that's
only to be expected. I can't explain this difference (unless you
did a clean install, and I've somehow copped an additional quirk
by merely upgrading). Curiouser and curiouser...
Well, kai, I am going to bed as well!
My bad, once i reread your email, I realized that as I was testing
I changed "<" to ">". That is why it worked it worked.
Now I can corroborate what you said.
Phew! Thanks very much for clearing that up, Deivy. I was trying to
come up with an explanation this evening while I was out - but drew a
complete blank. (Don't you just hate a mystery?) I really appreciate
the time that you have taken on this. :-)
This is a bad bug. Properties are not kept if you run from Script
Menu.
Obviously, adding a 'display dialog "something"' at the end of the
loop fixes the problems partially; since the script returns
something. But what is interesting is that if you cancel the run,
it will go back to the last value of the beginning of the loop, if
you do not return something.
Right. If saving changed properties is critical, even if an error
(such as a user cancellation) should occur, then it would need to be
trapped in some way. Otherwise, it would conclude execution of a
script without returning a value.
Nevertheless, since the added mystery doesn't really get away from
the original problem, I guess it still makes sense to drop it in
Apple's lap.
It is a nasty bug.
It certainly proved quite a headache to track down - mainly due to
the fact that, at first, the behaviour seemed to be a completely
random phenomenon. I confess it took me a while to work out what the
cause might be (especially since my conclusion didn't really seem
that rational)!
Thanks again for your help! :-)
Blush, wasn't much help, was it?
Sorry, you have to understand I am sleepy...
:)
On the contrary, Deivy. I really appreciate your willingness to work
through the problem with me. And thanks to all those who helped to
confirm and clarify the issue - which has now been filed under bug
ID# 4207835.
---
kai
_______________________________________________
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