Scratch

Sounds like a good idea. Support.

Maybe a master timer, but make timers available like variables? So any timer can be used on any sprite. This could also help communication between sprites. Maybe also a reset all timers block to.

benjamin2 wrote:

Why can't you make your own timer?

you might want a 1s1s project

Also if scratch slows down, it might put your timer off-track a bit.

when gf clicked
set [start time v] to (timer)
forever
  say ((timer) - (start time))
end

workaround:

when gf clicked
reset timer
delete (all v) of [timers v]

when i receive [reset timer v]
if <(timer id) > (length of [timers v])>
 add (timer) to [timers v] //save the starting time
else
 replace item (timer id) of [timers v] with (timer)
end

when i receive [get timer v]
set [result v] to ((timer) - (item (timer id) of [timers v])) //how much time since the last reset

Then, to reset a timer, set (timer id) to the number of the timer and broadcast [reset timer]

To get the value of a timer, set (timer id) to the number of the timer, broadcast [get timer], and the answer will be in the variable (result)

Don't use the reset timer block or all the timers you have so far will go off track.

Last edited by joefarebrother (2012-09-01 05:28:30)

([timer v] of [Sprite1 v])

Would that work for local/global?

Last edited by Molybdenum (2012-09-01 18:46:06)