The nice thing of these wrappers is that their properties have the same
names than timeout objects properties, so you can still do
oTimeOut.target
= ... , or oTimeout.period = ...
Thank you (and Jakob and James!) for sharing your lingo. I'm curious
about the use of the ancestor to store the referen
The nice thing of these wrappers is that their properties have the same
names than timeout objects properties, so you can still do
oTimeOut.target
= ... , or oTimeout.period = ...
Thank you (and Jakob and James!) for sharing your lingo. I'm curious
about the use of the ancestor to store the ref
The nice thing of these wrappers is that their properties have the same
names than timeout objects properties, so you can still do oTimeOut.target
= ... , or oTimeout.period = ...
Thank you (and Jakob and James!) for sharing your lingo. I'm curious
about the use of the ancestor to store the refere
Neat little script there... Its cleaner than the other example I found,
but it looks like the possible parameters are hardcoded and limited to 3:
(...)
...is that the adaptation you spoke of?
part of
In fact I usuall use one, eventually 2 arguments, so I found really faster
and enough for dail
Hi Séb,
Neat little script there... Its cleaner than the other example I found,
but it looks like the possible parameters are hardcoded and limited to 3:
on mTimeOut(me, aTimeOut) -
-- Called by the timeOut object ancestor at regular intervals
--
Hi
I believe I have used something written by Kerry that allowed callbacks
or parameters for timeouts...a sort of timeout wrapper class that worked
rather well as I recall...might be worth a dig in the archives, cause
unfortunately I can't find the link right now
I'm sorry I've missed this
At 16:32 Uhr -0500 11.11.2003, Mathew Ray wrote:
Google to the rescue:
http://maclux-rz.uibk.ac.at/maillists/direct-l/msg03740.shtml
Is that kind of what you mean?
yes, thanks, but I know, that it can be done with lingo.
it would be easier, if it would just be built in somehwere.
when I write a p
Sorry for the late reply, catching up on a bit of old mail...
I believe I have used something written by Kerry that allowed callbacks
or parameters for timeouts...a sort of timeout wrapper class that worked
rather well as I recall...might be worth a dig in the archives, cause
unfortunately I ca
Uh, is there some kind of spam harvester on lingo-l?
-- Forwarded Message
From: AntiSpam UOL <[EMAIL PROTECTED]>
Date: Mon, 20 Oct 2003 01:10:54 -0200 (BRST)
To: [EMAIL PROTECTED]
Subject: RE: Timeout object question
<http://antispam.uol.com.br> <http://www.uol.com.br
Yes. (assuming the last "this" is a "what")
The timeout object (and the 'me' if it's a behavior) are parameters which
are returned.
Makes it real convenient to "what.forget()" the calling timeout object if
necessary, without having to know/hardcode the name of the calling timeout
object. Also
At 13:57 Uhr -0400 19.10.2003, grimmwerks wrote:
I
mean, the work around is to have an object with properties AND a timeout as
a child, and it just functions as a pulse, checking the properties the
object changes (which is how I do it)
which might be how we all do it:
using either a property or a g
On 10/19/03 1:16 PM, "Alex da Franca" <[EMAIL PROTECTED]> spewed forth:
>> grimmwerks wrote:
>>> on test me, what
>>> put "this is:" && this
>>> End
>>
>> I guess you meant:
>>
>> on test me, what
>> put "this is:" && WHAT
>> End
Yeah, I was tired, and typing on a different computer,
At 12:53 Uhr -0300 19.10.2003, Agustín María Rodríguez wrote:
grimmwerks wrote:
on test me, what
put "this is:" && this
End
I guess you meant:
on test me, what
put "this is:" && WHAT
End
if only he had found something like:
pBlinker = timeout("blinker").new(1000, #test, me)
pBlinker.us
grimmwerks wrote:
on test me, what
put "this is:" && this
End
I guess you meant:
on test me, what
put "this is:" && WHAT
End
--
Agustín María Rodríguez | [EMAIL PROTECTED] | www.OnWine.com.ar
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/
Ok, simple question -
Birthing a timeout object, and checking what gets sent along with the
handler being called --
pBlinker = timeout("blinker").new(1000, #test, me)
And in that sprite:
on test me, what
put "this is:" && this
End
So I guess the calling timeout object gets passed as the
15 matches
Mail list logo
