Paddle2See wrote:

There isn't any way to stop it that I know of. A workaround is to make your own timer out of a variable and update it periodically in a loop. Then, when the loop stops, the variable will stop changing.

when gf clicked
forever
if <(timer_on) = [on]>
set (mytimer) to (timer)
end
end

The_Grits wrote:

Paddle2See wrote:

There isn't any way to stop it that I know of. A workaround is to make your own timer out of a variable and update it periodically in a loop. Then, when the loop stops, the variable will stop changing.

Sorta like this:

when gf clicked
forever
if <(timer_on) = [on]>
reset timer
set (mytimer) to (timer)
end
end

when gf clicked
set [timer v] to [0]
forever
if <(timer?) = [on]>
wait [0.01] secs
change [timer v] by [0.01]

sonicfan12p wrote:

Here's the script Paddle was referring to.

when gf clicked
set [timer v] to [0]
forever
if <(timer?) = [on]>
wait [0.01] secs
change [timer v] by [0.01]

The other scripts provided would only set the variable timer to the timer, not really a pause function, though they could work as a stop. This script allows the flexibility of pausing and then continuing repeatedly, accurate to a hundredth of a second. It can also be used as a dead stop.

DotDash wrote:

The_Grits wrote:

Paddle2See wrote:

There isn't any way to stop it that I know of. A workaround is to make your own timer out of a variable and update it periodically in a loop. Then, when the loop stops, the variable will stop changing.

Sorta like this:

when gf clicked
forever
if <(timer_on) = [on]>
reset timer
set (mytimer) to (timer)
end
end

Fixed

when GF clicked
repeat until <(timeOn?) = (0)>
Change (Timer) by [1] // not the timer..  But a different variable
wait (0.99) secs // A fail safe so (hopefully) the timer will be as accurate as possible.

scubajerry wrote:

sonicfan12p wrote:

Here's the script Paddle was referring to.

when gf clicked
set [timer v] to [0]
forever
if <(timer?) = [on]>
wait [0.01] secs
change [timer v] by [0.01]

The other scripts provided would only set the variable timer to the timer, not really a pause function, though they could work as a stop. This script allows the flexibility of pausing and then continuing repeatedly, accurate to a hundredth of a second. It can also be used as a dead stop.

I do not think this works very well. If the computer is busy doing other things, or even the program is busy running a RUN WITHOUT SCREEN REFRESH, for more than .01 seconds, the timer will miss increments.

sonicfan12p wrote:

scubajerry wrote:

sonicfan12p wrote:

Here's the script Paddle was referring to.

when gf clicked
set [timer v] to [0]
forever
if <(timer?) = [on]>
wait [0.01] secs
change [timer v] by [0.01]

The other scripts provided would only set the variable timer to the timer, not really a pause function, though they could work as a stop. This script allows the flexibility of pausing and then continuing repeatedly, accurate to a hundredth of a second. It can also be used as a dead stop.

I do not think this works very well. If the computer is busy doing other things, or even the program is busy running a RUN WITHOUT SCREEN REFRESH, for more than .01 seconds, the timer will miss increments.

That's why the increments are so small, so missing it won't mess you up too bad. However, it will work about as well as anything else, and I'd like to see someone come up with a more accurately scripted timer with pause function. Another solution is changing it to thousandth, or even ten thousandths of a second.

drmcw wrote:

I'd guess that smaller increments would be more inaccurate. I wouldn't rely on waits less than 1/10 certainly less than 1/100 of a second as being accurate at all. Rather they would be dependent on cpu speed and what other code is running. The most accurate use of the timer is to store its value at the start of an operation then subtract that from the timer value when it has finished, or reset at start and read at the end. So for your method I would rather use the biggest wait I could to make it more accurate.

when gf clicked
set [time difference v] to [0]
reset timer
forever
if <(timer on?) = [yes]>
set [my timer v] to ((timer) - (time difference))
else
set [saved timer v] to (timer)
wait until <(timer on?) = [yes]>
set [time difference v] to ((timer) - (my timer))
end

when green flag clicked
forever
set [time v] to (timer)

WarriorNinja983 wrote:

Do this. Instead of using the time block in the sensing, use a variable. Like this:

when green flag clicked
forever
set [time v] to (timer)

now when you want to show the timer block, show the varible instead.

sonicfan12p wrote:

when gf clicked
set [time difference v] to [0]
reset timer
forever
if <(timer on?) = [yes]>
set [my timer v] to ((timer) - (time difference))
else
set [saved timer v] to (timer)
wait until <(timer on?) = [yes]>
set [time difference v] to ((timer) - (my timer))
end

SonicFan, it looks like you can delete the SavedTimer line in the Wait loop.

Drmcw, thanks for the bright ideas. I think you'll find it best to only reset the system timer when starting the program. Letting the system timer run allows you to create as many user timers in your program as you like that use the system timer as their basic engine (otherwise resetting the system timer would goof up any timers that were enabled and running during the reset.)

Saving the system time is very clever. The numbers can grow very large, though, and lead to memory problems (I don't know what “too large” would be in Scratch, though.) Here's a way to only accumulate time and keep the system timer's accuracy: http://scratch.mit.edu/projects/16163344/#editor

The top version has a couple of extra lines to make it easier to follow the logic. The bottom version would be the one to use in a project.

Here's another approach: In order to save processor overhead, this project only updates the timer in whole second steps: http://scratch.mit.edu/projects/16160520/#editor

-Jason

deadjmau5 wrote:

Yea I tried that when its finished it broadcasts but that didnt really work XD

when I receive [Start Timer v]
set [Timer v] to [Whatever you want]
repeat until <(Timer(the variable you just created)) = [0]>
wait (1) secs
    
change [Timer v] by (-1)
end

when green flag clicked
forever
    
if <(time) < [ 0.01]> then
change [time v] by (0.01)
wait (0.01) secs
    
end
else
set [time v] to (timer) 
wait until <not <(timer) = (time)>>

end