Button Chording Timeout 'Feature'
Posted: Sun Mar 15, 2020 4:10 pm
XMBC Version: 2.19
Windows Version: 10 Pro
Mouse Information (brand/model): J-Tech 628P
Relevant Computer Information (CPU, RAM etc): i5, 24GB
Did the problem occur after an upgrade of XMBC? (If so, from what version?): no
Did the problem occur after a Windows update/upgrade? (If so, from what version?): no
How long have you used XMBC?: < 10 days
What language and keyboard layout do you use in Windows?: US English 104 Std
Clear description of the problem - try and include as much information as possible, including what button and mappings you are having problems with (if applicable).: I think I may have found a minor bug in the Button Chording Timeout.
I wanted to increase the timeout from 750ms to 1s. I clicked on the Up arriow in the widget and scrolled to "1,000" ms. When I saved the value, things didn't seem to work, so I checked the settings again. It seems that XBMC stored the setting as 1ms. Perhaps the comma messed things up? 999ms works fine.
If one inputs "1000" ms directly into the box and hits Enter, 1000ms is saved and everything works OK. So, it appears that the problem is with the scrolling method -- i.e., it adds a comma to the value -- not the value itself. Thoughts?
Regards,
-BW
Windows Version: 10 Pro
Mouse Information (brand/model): J-Tech 628P
Relevant Computer Information (CPU, RAM etc): i5, 24GB
Did the problem occur after an upgrade of XMBC? (If so, from what version?): no
Did the problem occur after a Windows update/upgrade? (If so, from what version?): no
How long have you used XMBC?: < 10 days
What language and keyboard layout do you use in Windows?: US English 104 Std
Clear description of the problem - try and include as much information as possible, including what button and mappings you are having problems with (if applicable).: I think I may have found a minor bug in the Button Chording Timeout.
I wanted to increase the timeout from 750ms to 1s. I clicked on the Up arriow in the widget and scrolled to "1,000" ms. When I saved the value, things didn't seem to work, so I checked the settings again. It seems that XBMC stored the setting as 1ms. Perhaps the comma messed things up? 999ms works fine.
If one inputs "1000" ms directly into the box and hits Enter, 1000ms is saved and everything works OK. So, it appears that the problem is with the scrolling method -- i.e., it adds a comma to the value -- not the value itself. Thoughts?
Regards,
-BW