Interesting and useful idea, Colin. Thanks a lot. I'd hope not to have to go down this road, but as you say, it may prove to be the more reliable one.
What did you do to synch your program to the timecodes in the list? Were you using the elapsedTime and polling for it on exitFrame or something along those lines? I'm still curious why this cuepoint messaging from the sound file to Lingo fails to work as it does in some files and not in others. It appears that flat lines or other areas of minimal amplitude in the waveform help make things work better. But not completely. At 12:11 AM 9/17/02 -0400, you wrote: >I used FindPosNear(). It will instantly tell you where in a list of values >another value lies. If you turn your timecodes into a list, and then use >findposnear() to see where you are, and then use that value to control >what text is seen, life will be much simpler, and more reliable. > >Example > >This statement identifies the position of a property in the sorted list >Answers, which consists of [#Nile:2, #Pharaoh:4, #Raja:0]: >findPosNear(Answers, #Ni) >The result is 1, because Ni is most closely matches to Nile, the first >property in the list. > >Here's an integer example: > >sometimes = [0,10,20,40,80,120] > >sort sometimes > >put findposnear(sometimes,13) >-- 3 > >The number returned is the first position that is greater in value than >the one you're checking. If you check with a value greater than the last >entry, then the position returned will be equal to the list count + 1. > >It's extremely useful! [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!]
