At 11:11 AM 9/6/2001 +1200, Sean wrote:
>Post your exitFrame/mouseEnter handler so we can take a look.
--frame script
in exitFrame
go to the frame
end
Slava's button handler; does not work, displays nothing in the projector's
message box:
--sprite behavior (attached to standard button)
on mouseEnter
PUT "In Slava's mouseEnter"
pass
end
Sean's hack; works, displays the message in the projector's message box:
--sprite behavior (attached to standard button)
property pMouseWithin
on mouseEnter me
PUT "In mouseEnter of Sean's button."
pMouseWithin = true
pass
end mouseEnter
on exitFrame me
if rollOver(me.spriteNum) then
if not pMouseWithin then
mouseEnter(me)
else
mouseWithin(me)
end if
else
if pMouseWithin then
mouseLeave(me)
end if
end if
end exitFrame
on mouseLeave me
pMouseWithin = false
pass
end mouseLeave
QUESTION: What is going on? In Sean's hack, the mouseEnter handler is
kicked into action by a call from exitFrame. But that call depends on a
property value that was set in the mouseEnter hanlder. So was mouseEnter
executed before being kicked by exitFrame, or wasn't it? And why is Slava's
mouseEnter not working?
The failure of Slava's mouseEnter (and mouseLeave, and mouseWithin)
handlers is consistent and totally reproducible (in the current project,
which is big). The mouseEnter of EVERY sprite in the frame fails to
execute. This happens only in a projector, when the movie is a MIAW. The
same mouseEnter handlers attached to the same sprites in the same frame
work fine in authoring.
[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!]
