• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Script Menu in Tiger: non-persistent property bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Script Menu in Tiger: non-persistent property bug?


  • Subject: Re: Script Menu in Tiger: non-persistent property bug?
  • From: deivy petrescu <email@hidden>
  • Date: Sun, 7 Aug 2005 14:24:10 -0400


On Aug 7, 2005, at 12:33, kai wrote:


On 7 Aug 2005, at 16:55, deivy petrescu wrote:


Script Menu
-----------

Run 1:
------

--> Test #1
--> Test #2
    (etc...)
--> Test #9
--> Test #10

Run 2:
------

--> Test #1
--> Test #2
    (etc...)
--> Test #9
--> Test #10



Not on my machine!

I get 11, 12...


Ooer... what gives here, then?


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.
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.




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.


Thanks again for your help! :-)


Blush, wasn't much help, was it? Sorry, you have to understand I am sleepy... :)

---
kai


Deivy

_______________________________________________
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


  • Follow-Ups:
    • Re: Script Menu in Tiger: non-persistent property bug?
      • From: kai <email@hidden>
References: 
 >Script Menu in Tiger: non-persistent property bug? (From: kai <email@hidden>)
 >Re: Script Menu in Tiger: non-persistent property bug? (From: deivy petrescu <email@hidden>)
 >Re: Script Menu in Tiger: non-persistent property bug? (From: kai <email@hidden>)
 >Re: Script Menu in Tiger: non-persistent property bug? (From: deivy petrescu <email@hidden>)
 >Re: Script Menu in Tiger: non-persistent property bug? (From: kai <email@hidden>)

  • Prev by Date: Re: Script Menu in Tiger: non-persistent property bug?
  • Next by Date: Re: Finder Info to get real audio media source URL
  • Previous by thread: Re: Script Menu in Tiger: non-persistent property bug?
  • Next by thread: Re: Script Menu in Tiger: non-persistent property bug?
  • Index(es):
    • Date
    • Thread