[etoys-dev] Timers

Steve Thomas sthomas1 at gosargon.com
Sat Jun 26 22:58:12 EDT 2010

Why a timer variable on each playfield as opposed to a timer object?
The timer object could also be a stopwatch (yes, you could create a variable
and set it to the timer value on some event, but a 'stop timer' tile seems
simpler). Also, you would only have running intentionally created timers,
the current implementation would cause timers to run which could impact
performance (albiet minimally).


On Sat, Jun 26, 2010 at 12:16 PM, Bert Freudenberg <bert at freudenbergs.de>wrote:

> This is related to the discussion of non-accurate tick rates:
> http://tracker.squeakland.org/browse/SQ-708
> There currently is no good way to measure real time in Etoys. The Clock
> object is only accurate to one second.
> So I'm proposing to have a global timer, in seconds, but with milli-second
> resolution. There would be a tile for accessing it in the world's
> "playfield" category (actually any playfield / holder).
> This would allow to do animations etc to proceed in real time, independent
> of the actual tick rate of a script.
> I just posted a proposed implementation to the inbox (Etoys-bf.31). Also,
> find attached an example project.
> Would that be generally useful?
> - Bert -
> _______________________________________________
> etoys-dev mailing list
> etoys-dev at squeakland.org
> http://lists.squeakland.org/mailman/listinfo/etoys-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakland.org/pipermail/etoys-dev/attachments/20100626/31b91058/attachment.html

More information about the etoys-dev mailing list