• 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: kai <email@hidden>
  • Date: Sun, 7 Aug 2005 16:38:59 +0100


On 7 Aug 2005, at 15:44, deivy petrescu wrote:

Kai,
I can corroborate that!

Thanks, Deivy - that at least reassures me that my machine is behaving as well as can be expected - under the circumstances. ;-)


However, if you wrap this script in a repeat loop, say
--
property n : 1
repeat 10 times
    display dialog "Test #" & n giving up after 1
    set n to n + 1
    if n < 4 then n
end repeat
--

it works as expected in SM.

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. Compare the following results, for example:


Script Editor
-------------

Run 1:
------

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

Run 2:
------

--> Test #11
--> Test #12
    (etc...)
--> Test #19
--> Test #20


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

Run 1:
------

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

Run 2:
------

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

On 7 Aug 2005, at 16:28, Paul Berkowitz wrote:

Confirmed. And it has nothing to do with Script Editor itself, nor even Data
Fork scripts. The same thing happens with compiled scripts made in Script
Debugger 3, both Data Fork and Resource Fork scripts. It also has nothing to
do with just getting the value after defining it (like in the iApps).
Interpolating an extra line or lines after setting n makes no difference.

Thanks for the additional confirmation, Paul. I'll file a bug.

If you add a simple

    return

at the end, then it never progresses past #1 - no changes are ever saved.
But return any "dummy" value - as you say - like 101 - and it keeps
incrementing every time.


Oy.

Quite...

---
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
  • Follow-Ups:
    • Re: Script Menu in Tiger: non-persistent property bug?
      • From: Bill Cheeseman <email@hidden>
    • Re: Script Menu in Tiger: non-persistent property bug?
      • From: deivy petrescu <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>)

  • Prev by Date: Re: Inheritance and Loaded Libraries
  • Next by Date: Re: Script Menu in Tiger: non-persistent property bug?
  • 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