Re: lingo-l Bug of the week

2004-02-11 Thread roymeo
I think you're also missing a very important thing in that beginSprite handler!! on beginSprite me tempVar = timeOut(test).new(500, #doSomething, me) end beginSprite You need to set the returned value of that timeout().new() to a variable, or you get hemorrhoids and excessive eye-booger

lingo-l Bug of the week

2004-02-10 Thread Kerry Thompson
I managed to get the startMovie handler called 7 times. I'm willing to let you guess how I managed that before I reveal yet another Stupid Lingo Trick. Cordially, Kerry Thompson [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post

Re: lingo-l Bug of the week

2004-02-10 Thread Colin Kettenacker
Kerry Thompson [EMAIL PROTECTED] on 2/10/04 9:53 AM wrote: I managed to get the startMovie handler called 7 times. I'm willing to let you guess how I managed that before I reveal yet another Stupid Lingo Trick. on stupidTrick me repeat with i = 1 to 7 startMovie end repeat end

Re: lingo-l Bug of the week

2004-02-10 Thread Buzz Kettles
At 12:53 PM -0500 2/10/04, you wrote: I managed to get the startMovie handler called 7 times. I'm willing to let you guess how I managed that before I reveal yet another Stupid Lingo Trick. Cordially, Kerry Thompson I'm sure that you didn't use a repeat loop a counter - that would be intentional

RE: lingo-l Bug of the week

2004-02-10 Thread Kerry Thompson
on stupidTrick me repeat with i = 1 to 7 startMovie end repeat end stupidTrick Kidding... really:) :) That would be on reallyStupidTrick ^_^ Mine is much more subtle--took me two hours to figure out what was happening. Cordially, Kerry Thompson [To remove yourself from this

Re: lingo-l Bug of the week

2004-02-10 Thread grimmwerks
Something to do with timeout objects? [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

Re: lingo-l Bug of the week

2004-02-10 Thread Warren Ockrassa
On Feb 10, 2004, at 11:53 AM, Kerry Thompson wrote: I managed to get the startMovie handler called 7 times. I'm willing to let you guess how I managed that before I reveal yet another Stupid Lingo Trick. 7 MIAWs? ;) -- WthmO [To remove yourself from this list, or to change to digest mode, go

RE: lingo-l Bug of the week

2004-02-10 Thread Pranav Negandhi
Funny...there are seven cardinal sins too, right? Kerry, what have you been upto? Is this a divine sign to start afresh? Or do you just have 7 timeout objects floating around? Pranav Negandhi concept-I www.cimultimedia.com snip At 12:53 PM -0500 2/10/04, you wrote: I managed to get the

RE: lingo-l Bug of the week

2004-02-10 Thread Kerry Thompson
Did you link this movie as an LDM in itself? Heh. That would do it. But no, that's not it. Cordially, Kerry Thompson [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,

Re: lingo-l Bug of the week

2004-02-10 Thread Sean Wilson
I managed to get the startMovie handler called 7 times. I'm willing to let you guess how I managed that before I reveal yet another Stupid Lingo Trick. You created 6 timeout objects in prepareMovie and none of their targets contained startMovie handlers? [To remove yourself from this list, or

RE: lingo-l Bug of the week

2004-02-10 Thread Kerry Thompson
You created 6 timeout objects in prepareMovie and none of their targets contained startMovie handlers? Almost--but I would have caught that right off. The subtle part is that beginSprite happens before startMovie. I think that only applies to sprites in frame 1, but not sure. Cordially,

Re: lingo-l Bug of the week

2004-02-10 Thread grimmwerks
On 2/10/04 1:26 PM, Kerry Thompson [EMAIL PROTECTED] spewed forth: TimeOut Objects get startMovie events. If you don't trap them, they get passed on up the line to the movie level. I put this: on startMovie nothing end Hmm. Well I've got a main startmovie handler, and am birthing timeout

RE: lingo-l Bug of the week

2004-02-10 Thread Buzz Kettles
At 2:12 PM -0500 2/10/04, you wrote: You created 6 timeout objects in prepareMovie and none of their targets contained startMovie handlers? Almost--but I would have caught that right off. The subtle part is that beginSprite happens before startMovie. I think that only applies to sprites in

Re: lingo-l Bug of the week

2004-02-10 Thread Mathew Ray
OCH! I need to make a big ol' order of events table for director and hang it on my wall. Is there a little Pnemonic like PEMDAS or the like for director? :0) I can totally see this happening with one of my director projects... Recently I had a similar issue but with no sensical reason in a

RE: lingo-l Bug of the week

2004-02-10 Thread Kerry Thompson
OCH! I need to make a big ol' order of events table for director and hang it on my wall. Is there a little Pnemonic like PEMDAS or the like for director? I don't know a mnemonic, but there's something almost as good--Bruce Epstein's Director in a Nutshell. It's out of date on a lot of things

RE: lingo-l Bug of the week

2004-02-10 Thread Kerry Thompson
For me I would only ever get two startMovie event calls regardless of how many sprites I attached the timeout script to. For curiosity sake Kerry, how are you managing to get 6 startMovie events triggering. I have six timeOuts, one for each sprite. Each sprite's timeOut has a different

RE: lingo-l Bug of the week

2004-02-10 Thread Jakob Hede Madsen
At 13:26 -0500 10/02/04, Kerry Thompson wrote: I put this: on startMovie nothing end Which is the right thing to do, but there's also the additional safetynet-version. In your actual movie-level startMovie handler: on startMovie param1 if param1.objectP then (*)return end if ...