Thank you Irv. I had not realized the distinction even though it is
clearly noted in the docs (v10). I guess I have not had a score
arangement that got me into trouble with such, but I'll start using it
now to be on the safe side.
Lee C
Irv Kalb wrote:
The problem is that the cursor (and visibility) are not actually
sprite properties, but instead are properties of the channel. That
is, they do not get reset when the playhead leaves a sprite span like
almost all other sprite properties.
If you set a cursor in a beginSprite and do not clear it in the
matching endSprite handler, the cursor will still be set for any other
sprites that appear in the same channel anywhere else you may navigate
to within the same movie. Clearing it in the on endSprite handler
prevents this problem.
Irv
At 11:29 AM -0500 12/21/04, KLGC Studio wrote:
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!]
