Weird Idle behavior
chris at carroll-davis.co.uk
Mon Mar 27 14:17:16 EST 2006
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!
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?
> 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
>> 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
>> 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!?
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the Use-livecode