>Let me re-state: the question I was responding to related to a user having
>set the tempo channel to "Wait for Mouse Click or Key Press", and who
>couldn't then understand why mouseEnter handling 'appeared' to be not
>working.
>
> > The wait-for mouse click (or keypress) was probably added because it
> > makes it really easy to create read-this-then-click types of page
> > sequences.
>
>It's useful to understand the history of where these elements came from;
>but
>again - the docs say nothing about the side-effects of using this
>particular
>feature, hence the possibility for confusion.
>
>I'm reasonably sure we, collectively, have that one cleared up.
>
Actually, Kerry had guessed correctly what I had done - he mentioned it in
an earlier post:
I had set it to wait (a number of seconds) command. Very astute of him!
And thanks for helping me discover my mistake. I appreciate it.
The thing was when I used this command - the mouseEnter, mouseLeave
commands will not work properly.So I removed it.
However the scene finished too quickly in the score. So I used an
exit frame event.
Is that the 'correct' way of doing it?
But in doing this, the movie doesn't run properly.
When I input sound, the sound is abruptly cut-off because the playhead has
reached the number of frames I stipulated.
So if my frames were very short, I would be in a greater dilemma...
Any suggestions to improve this would be greatly appreciated.
Also, lingo scripts in a handler execute from the top first statement
downward to the last statement. Is this correct? Or does it execute from
bottom up? Please advise.
Thanks
Genevieve
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
[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!]
