Handlers in movie scripts are available globally. So, if you have an on mouseUp handler if a movie script, and nothing else is "catching" the mouseUp events, then they get sent to the on mouseUp handler in the movie script.

If/when you have an on mouseUp handler in a behavior, it only applies to the sprite or sprites to which you have that behavior attached. For example, if you have a sprite in channel 1, and you attach such a behavior, then if you do a mouse up while over that sprite, then Director will send the mouseUp event to that behavior.

If you just have this code in a behavior script and don't attach the behavior to a sprite, then the code will have no effect since it is not really active at all. Specifically, there will not be any "instances" of this script running.

Hope this helps,

Irv



At 5:37 PM -0400 5/20/04, Paul Schulman wrote:
I am setting up movie in which just horizontal mouse locations are recorded in
lists. In a movie script, I initialized some (global) lists in a startMovie
handler. Then in a mouseUp handler I have this case statement that adds the
mouseH to one or the other of the lists.


This works nicely if this handler is in the movie script.  If I put it in a
behavior script, even declaring the lists as global, it doesn't work.  What
principle am I missing?

Paul Schulman
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]


--

Multimedia Wrangler.

[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]

Reply via email to