What you mention is the technique I use Irv, but without the endSprite
part. Maybe I've just never run accross a situation where the reset was
necessary in on endSprite?
Lee C
Irv Kalb wrote:
You might want to try the syntax that Chris suggested but in a
different place. I always use the sprite(spriteNum).cursor syntax,
but I put it in the beginSprite and endSprite handlers:
property spriteNum
on beginSprite me
sprite(spriteNum).cursor = 280
--anything else you want to do here
end
on endSprite me
sprite(spriteNum).cursor = 0 -- -1 sometimes screws things up
later
-- anything else you want to do here
end
This way, there is no need to set and reset in every mouseEnter and
mouseLeave.
Irv
[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!]