> No bugs that I know of, but it's a pretty new feature, and
> judging by the
> traffic on the list, only the adventurous are using them.
That's me - Karina the Barbarian 8-@
> 1. Make sure you are not instantiating the object multiple
> times--e.g., in
> an exitFrame handler. I've followed your posts, though, and it seems
> unlikely you would make this error.
Thanks Kerry, same to you :)
And you're right, I didn't...
What I had was one innitiation from either of two possible handlers, running
it once and then forgetting it from the handler that the timeOut was calling
(just for a small pause - beats the other pausing methods, when it works)
And it was working fine, at first - but then suddenly I started getting all
these errors.
And do you know why? I just discovered the culprit: a simple old fashioned
"on timeOut" in my movie script... When I commented that out, just a minute
ago, The timeOuts started working again! Bug? or Feature?
Hmm.. I wander what the good old timeOutScript would do?
Also, Alex wrote:
>I had recently had a problem that was very much alike. The answer
>was simply the sprite wasn't present in the score anymore because I
>jump to a frame in which I didn't used the sprite.
In this case, that wasn't the problem - even a test timeOut on startMovie
returned "object not found"... But it's solved now.
Oddly enough, I had an opposite problem, in a previous project - I "forgot"
the timeOut on end sprite, but it would still come back to haunt me, despite
the fact that it was definitely removed from the timeOut list. I solved that
one by a couple of overkills that I'm not proud of - eg. checking for an
"active" flag before executing the target hanlder, setting the timeOut to a
redundant variable and setting the variable to Void after the "forget" -
like I said, I'm deeply ashamed of myslef ;)
>
> I've used timeouts quite a bit now, and not run into the problem you
> described, so I *think* they're pretty stable. They take a
> lot of CPU time,
> though, and a long timeout running can bog down your system.
> Other than
> that, they're way cool.
Agreed. But I didn't know about the CPU hogging. It's always good to be
aware of these things.
Karina
[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!]
