Well, no. Unfortunately. I had idlerate set to 0 for best update
speed, but setting back to default of 200 makes no improvement.
:-(
Idle *is* being called. It's just not updating the display!
C
On 27 Mar 2006, at 19:50, Mark Smith wrote:
Not sure if it's the answer, but have you checked out the idleRate
property in the docs?
Best,
Mark
On 27 Mar 2006, at 19:25, Chris Carroll-Davis wrote:
Hello folks -
here's a weird one... I'm updating a timer on idle:
On idle
global StartTicks
if StartTicks = "" then exit idle
updateTimer
wait 1 millisecond with messages -- attempt at kludge!
end idle
which just draws an arc graphic to give visual feedback
On updateTimer
global StartTicks, timeLimit
If StartTicks = "" then exit UpdateTimer
put 180+(180/(timeLimit * 60) * (the ticks - StartTicks)) into a
set the startangle of grc "timer" to a
if a >= 360 and StartTicks <> "" then
TimesUp
exit updateTimer
end if
end updateTimer
This goes along fine, timing out after the timelimit ... except
that it doesn't update the display!! If I call "updateTimer"
from a repeat loop, it works fine. Has anyone come across this
before? Anyone got a workaround!?
Chris
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
