Re: lingo-l Bug of the week
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 production. roymeo At 04:01 PM 2/10/2004, you wrote: Kerry Thompson [EMAIL PROTECTED] on 2/10/04 10:26 AM wrote: I have a behavior on some sprites in frame 1. It creates a timeOut object to animate itself. 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 in my behavior, and life is good again. Well I'll be darned. Thanks to Bruce's DIAN and LIAN books I too was well aware that beginsSprite in frame 1 was called before startMovie, however why on earth would a timeout object triggered by a behavior attached to a sprite in frame one trigger extra startMovie events? Yet another reason to avoid using frame one I suppose. Anyway I tried attaching this behavior to multiple sprites in frame one: on beginSprite me timeOut(test).new(500, #doSomething, me) end beginSprite on doSomething me nothing end doSomething And added this movie script: on startMovie put startMovie end startMovie 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. ck -- Cheap Domain Registration | Web Hosting | Email Packages | + more Fantastic prices -- Even better service. http://www.hosttohost.net [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!] -- roymeo(AT)brokenoffcarantenna.com -- i used to love you back when you wrote poetry [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!]
lingo-l Bug of the week
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 messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l Bug of the week
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 stupidTrick Kidding... really:) ck -- Cheap Domain Registration | Web Hosting | Email Packages | + more Fantastic prices -- Even better service. http://www.hosttohost.net [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!]
Re: lingo-l Bug of the week
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 this doesn't sound intentional did you call startMovie from the beginSprite handler of 7 sprites? -Buzz [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!]
RE: lingo-l Bug of the week
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 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!]
Re: lingo-l Bug of the week
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 Lingo. Thanks!]
Re: lingo-l Bug of the week
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 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!]
RE: lingo-l Bug of the week
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 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 snip [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!]
RE: lingo-l Bug of the week
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, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l Bug of the week
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 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!]
RE: lingo-l Bug of the week
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, 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, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l Bug of the week
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 objects as properties to a sprite/behavior, with it directing itself to a handler within the behavior as it's own handler, and I've not seen my main startmovie handler being called. Are you just creating timeoutobjects as their own little thing, ie calling a main handler rather than as a slave to a behavior/calling a behavior handler? [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!]
RE: lingo-l Bug of the week
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 frame 1, but not sure. true - startMovie has happened already for all other frames bad frame 1 ! -Buzz [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!]
Re: lingo-l Bug of the week
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 flash project. Worked fine when run from the hard drive, or over the network, but when the website was burned on a cd and viewed in IE, the project failed. It didn't load in IE, but was fine in Firebird and Safari. Pushing everything, including class/function declarations, content, down a frame made it start working. Totally bizarre. I guess it's another good reason to not put stuff in frame 1 unless you really have a reason to... ~Mathew Kerry Thompson 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 frame 1, but not sure. 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, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l Bug of the week
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 now, but the basic structure of Director hasn't changed much since he last updated it. It has excellent references on event hierarchy. 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, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l Bug of the week
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 name. 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, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l Bug of the week
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 ... Which by the way, also offers an entry-point (*) for debugging unwanted events, so you could have shaved those two hours. [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!]
