Re: Passing *possible* variables to a handler
Re: Passing *possible* variables to a handler
- Subject: Re: Passing *possible* variables to a handler
- From: Paul Berkowitz <email@hidden>
- Date: Sun, 14 Jul 2002 10:37:10 -0700
On 7/14/02 10:09 AM, "Arthur J. Knapp" <email@hidden> wrote:
>
> Date: Sat, 13 Jul 2002 12:00:14 +0100
>
> From: has <email@hidden>
>
> Subject: Re: Passing *possible* variables to a handler
>
>
> set wrappedList to wrapList({})
>
>
> --populate the list with N items
>
> repeat 1000 times
>
>
> set wrappedList's end to 0
>
>
Now THAT is COOL !!!
>
>
So all list "properties" can be inherited by a script object, ie:
>
>
wrappedList's some item --> random member of list
>
wrappedList's reverse --> reversed list
1) I see I'm going to have to study all this. I still can't make out what's
going on, but I'll try. I really will. Uggh.
2) On a related topic, I think I've seen both of you (maybe just Arthur?)
shove script objects into properties of your main scripts, perhaps with a
'run script' thingy? Is this necessary/useful/whatever? When?
3) And finally - I have occasionally used the Serge technique in a handler
which itself is revisited many times in the main script's repeat loop. As
far as i can see, that means I'm having to constantly re-initialize the
embedded script object a zillion times. Would this be a situation where the
script object in the handler could just be initialized once and its values
(the list which forms its own property) replaced a zillion times instead?
The script object would then have to be a main script property, yes? (Maybe
this is related to no. 2) above?) Or why not in that case just make the list
a main script property or global and use 'my' a la Nigel - replacing its
values each time?
--
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.