if you want the mouseleave handler to execute on mouseup try

sendsprite(me.spritenum,#mouseleave)within the mouseup handler this should
reset the cursor to the original settings.

be sure to send the event before you transfer control(before the go frame
command).



Vijay

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of mirianam
Sent: Tuesday, October 23, 2001 9:57 PM
To: lingo list
Subject: <lingo-l> Best way to organize


Hello all
Just some general questions about the best way to work.

I have made some rollover behaviours and some change cursor behaviours.
These are 2 separate behaviours and when I attach them to a sprite there
are, of course, multiple behaviours. Both these use mouseEnter and
mouseLeave.
My question is - is this OK, having 2 separate behaviours using the same
mouseEnter and mouseLeave - or is it better to combine the 2 into one
behaviour. So far I have had no problems but I worry if this is the best
way.

My second question is about the cursor change. On mouseEnter I change
the cursor to a finger and on mouseLeave it goes back to arrow but of
cousre when the sprite is clicked and movie goes to another frame the
cursor remains a finger (no mouseLeave executed). Should I add a score
script to on prepareFame to go back to arrow? or some other way.

I apologize if this is strictly not a lingo question but I'm not sure
what the best way is to organize these things. Any suggestions would
really be appreciated.
Thanks


[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/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!]



[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/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