> >My point was that, IMO, the ability to "Wait for ..." shouldn't have been > >added, or should have come with the warning message that "If you utilise > >this feature your frame-rate will turn to molasses, regardless > of what your > >'frame clock' is set to." > > > >As evidenced, new users have trouble understanding what went wrong. > > If one sets the Tempo (frame rate) slow, Director's animations go > slow - I really don't see the confusion in this (see below)
No confusion here. 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. -Sean. [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!]
