I understand your thinking and was prepared to go down that road before I first wrote to the list about this. Some cuepoints are as little as .3 seconds apart. But as I mentioned, I checked the procession of events using the on cuePassed handler and got precisely the results I enumerated in a post late last night. They were that in some cases, later cuepoints weren't passed to Lingo until after the file finished playing.
So for whatever reason, that wasn't the solution. I remain curious as to why certain files, two in particular, are causing this problem with Lingo, regardless of the Lingo handlers, commands or properties. Is it Director or is it the .wav file? Fortunately, Colin's solution makes the question academic in my case, but it would be nice to know. At 08:27 AM 9/17/02 -0700, you wrote: >Checking the mostRecentCuePoint() periodically can often miss points when >they occur close together. That method checks after the event has >happened. It doesn't tell you when it occurred, only that it did, at some >time in the past. > >As Irv has mentioned, if you put your response code in an 'on cuePassed >handler', you should get responses as every cue occurs. [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!]
