The bug I have found is very annoying, and it seems it SHOULD be a simple fix. Currently, the <Down> and <Repeat> commands are generated properly. However, the <Up> event is not generated properly. Instead of generating the <Up> event after the 150ms timeout since the last event, it generates it exactly 2sec after the last event. It seems this 2 sec is hard-coded in the plugin, and is a serious deal-breaker for using this feature. 2sec is an eternity in HTPC terms. It will generate an <Up> event if a different command is recieved within that 2 sec, which seems correct, it's just this 2sec is wrong. Instead of 2 sec, it should use the value in the debounce parameter.
like i said, simple fix.
I didn't know whether this belongged here or at the Promixis forum, but i figured I'd try here first.
Thanks again for the great device, it has worked well for me for many years, but this bug is limiting my systems evolution.
example Girder Log:
- Code: Select all
15:13:08:329 5/1/2008 USB-UIRT driver 631B050041F5 <Up>
15:13:06:329 5/1/2008 USB-UIRT driver 631B050041F5 <Repeat>
15:13:06:204 5/1/2008 USB-UIRT driver 631B050041F5 <Repeat>
15:13:06:079 5/1/2008 USB-UIRT driver 631B050041F5 <Repeat>
15:13:05:938 5/1/2008 USB-UIRT driver 631B050041F5 <Repeat>
15:13:05:813 5/1/2008 USB-UIRT driver 631B050041F5 <Repeat>
15:13:05:688 5/1/2008 USB-UIRT driver 631B050041F5 <Down>