Re: Script Hierarchy
On Sat, 3 Feb 2007 15:04:29 +0100, David Bovill wrote: Is it the case that libraries of the same type (forn,used, and back) are effectively all in one flat space - as if they were in a single script, and that the order only affects the order the scripts are added to this space (in case there are multiple handlers of the same name)? Yup... :-) Ken Ray Sons of Thunder Software, Inc. Email: [EMAIL PROTECTED] Web Site: http://www.sonsothunder.com/ ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Script Hierarchy
I guess there is one difference with regard to the way pass works? on mouseUp testHierarchy end mouseUp on testHierarchy answer 1 pass testHierarchy end testHierarchy on testHierarchy answer 1 end testHierarchy In that the second testHierarchy does not get called in a single script - but would if it were in the right place in the hierarchy of used stacks for instance? ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Script Hierarchy
Which makes me think that pass works according to a strict hierarchy. If you pass a handler call it will nto find anything in any of the libraries below it in the hierarchy. While on the other hand a straight call to the handler from a script behave completely differently in that it will be picked up by any of the libraries regardless of whether the calling handler was above the found handler in the hierarchy. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Script Hierarchy
David Bovill wrote: Which makes me think that pass works according to a strict hierarchy. If you pass a handler call it will nto find anything in any of the libraries below it in the hierarchy. Right. Passing a handler or function call follows the message hierarchy. While on the other hand a straight call to the handler from a script behave completely differently in that it will be picked up by any of the libraries regardless of whether the calling handler was above the found handler in the hierarchy. I think a lot of your questions are answered here: http://support.runrev.com/scriptingconferences/ Download the conference stack about the message hierarchy. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Script Hierarchy
Thanks - taking a look. This is my fourth version of a recursive function to walk the message hierarchy - itching to get it just right :) ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Script Hierarchy
David Bovill wrote: Thanks - taking a look. This is my fourth version of a recursive function to walk the message hierarchy - itching to get it just right :) You might want to check the list archives -- there have been a couple of threads on this and a number of good handlers presented. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
