>well, yes, but why should I need to. As I understood it the
>new(timeOut...) object stuff is good for sending an event at regular
>intervals whilst the <on timeOut> handler and related commands were for
>the specific purpose of keeping a track of how long since any user last
>interacted with the programme <snip>
Jon,
I think I'm hearing a misunderstanding of the timeOut object.
First, though, do you have a handler tPause in the script that creates the
timeOut object? If you're passing the me parameter, your handler has to be
in the same script.
Now, the basic idea of the timeOut object is to ask the system to notify
you (call a handler) when a certain amount of time has gone by. You can use
different objects to time different things, using different scripts, or you
can use one object to do different things using a case or if... then statement.
For example, I'm writing a program now with two timeOut objects. One calls
a handler, moveMe, in a behavior attached to a sprite. This causes the
sprite to move around the screen. In this instance, I've set this timeOut
object to call moveMe 100 times a second.
After a period of time has passed--say, 15 seconds--the moving sprite finds
a nearby sprite and locks onto it. To do this, I create another timeOut
object, set to call lockOn after 15 seconds. This lockOn handler is also in
the same behavior.
In both cases I'm passing the me parameter, and everything works just fine.
I would:
1. Make sure your handler is in the same script
2. As Jakob suggested, make sure your script is a behavior.
Cordially,
Kerry Thompson
Sr. Interface Engineer
Learning Network
[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!]
