Antirepeat

[Ron]

Thanks for the report, I'm actually currently working on this

http://www.girder.nl/phpBB2/viewtopic.php?t=1503

The first alpha release will be here later today.

[Ron]

Maybe you can elaborate a little on your antirepeat problem as you say the alpha release didn't fix it.

[Snakebite]

Hello,

while debugging my plugin I noticed that when I link an event to a command that takes a long time to execute, that execution time "counts" when the event's antirepeat time is measured. My remote is quick to repeat keypresses so I usually have 500 ms antirepeat on every event. But still, Girder will register a double keypress because the command (triggered by the first event) took more than 500ms to execute. It's as if Girder is working like this:

1. get next event from queue
2. read clock
3. if within antirepeat timeout then goto 1
4. execute command
5. goto 1

Wouldn't it be more useful to read the clock when the event is ENqueued as opposed to DEqueued? 500ms should be real time, not Girder-time?

[Snakebite]

Aha, I didn't read that thread very carefully before (or I didn't quite understand it). Great!