2014-10-29, 18:24
(2014-10-28, 20:34)popcornmix Wrote:It sounds like a lot of work for just a slightly better user experience. Though if it's perfection you're striving for... ;-)(2014-10-28, 20:01)Forage Wrote: Works like a charm! I wasn't able to reproduce the double key issue. Great to see that it has been properly fixed instead of using a work-around.
One thing I did notice is that responding becomes relatively slow when you press a key really, and I mean almost abnormally, fast. It actually goes faster when you press slightly less fast. Could this be because of the time-out increase?
I used the shutdown menu as a low action list instead of e.g. the movie library with heavier loads on switching entries for testing.
I do want to be able to navigate relatively fast every once in a while and the delay is on the fringe of being possibly annoying right now.
I'm happy with this being fixed in it's current state nevertheless.
Yes. The Panasonic TVs generate two button press events if you hold the button for more than about 250ms (which is a quite normal duration for a button press).
The workaround is to reject a second button if it occurs within ~300ms of the first.
Unfortunately two rapid presses produces the same result as the single leisurely press which means they also get filtered out.
I've been working on improving the behaviour of CEC remotes.
Currently when you hold down a button it repeats at a rate chosen by the TV. Typically that is between 2 and 5 times per second (varies with TV manufacturer).
This is a much slower repeat than a keyboard (repeats 12 times per second) which makes scrolling long lists slow with CEC.
My plan is to (optionally) ignore the CEC presses and generate a different stream of presses with a configurable repeat rate, (e.g. allowing 12 repeats per second).
Unfortunately CEC devices are pretty inconsistent in behaviour. It can be impossible to distinguish a few quick presses from a single longer press.
Some devices generate button released events which are useful, but the Sony in front of me doesn't always...
So I'll allow a few settings to tweak how it behaves and we'll see if people prefer it (the default will behave how it always has).
Not ready for tonight, but maybe tomorrow night.
Making these options available in the UI settings is handy during testing, but it introduces quite some complexity for the average user who are likely to mess things up. I'd recommend making them config file only settings at some stage and maybe introduce them again in the UI when there's a distinction between normal and expert settings on that level.
Thanks for the effort though, I sure will test the latest nightly and report my findings.