[mythtv-users] Foiled by lirc - yet again

Daniel Carter dantheperson at gmail.com
Thu Sep 1 21:23:03 UTC 2011

On 31 August 2011 22:26, Kevin Kuphal <kkuphal at gmail.com> wrote:
> I'm pretty sure this is a QT limitation in that it ignores SHIFT operators?

If it was a QT limitation, then you wouldn't be able to create a
keybinding in the frontend that uses SHIFT.  Thing is you can create
such a keybinding using the frontend - so that part notices the shift
operator just fine, but then the rest of the frontend ignores it, so
the keybindings don't work.

I've since found out this is intentional behaviour, so that
keybindings are case insensitive,

I see why you would want to make the bindings case-insensitive so that
if you are using a keyboard on a PC you don't have to worry about
whether caps lock is on.  But on a PVR using a remote where caps lock
does not exist it's not really a worry.  Furthermore if you are going
to make it case insensitive, then make the part of the app that sets
keybindings case insensitve too, so you press a button on your remote,
it sends Ctrl+Shift+P, the binding app ignores the shift and records
Ctrl+P.  Then during normal usage you press Ctrl+Shift+P, the app
ignores the Shift, and pretends you pressed Ctrl+P which is consistent
and so matches the binding.  At the moment you have to understand what
is going on behind the scenes and use a PC keyboard to set a Ctrl+P
binding that will work with your remote sending Ctrl+Shift+P.

Seems like we still have to go the route with lirc, using the driver
that emulates an IR receiver from a standard input device, 5 layers of
mapping, and lots of tedious manual setup, when if only myth didn't
ignore SHIFT, it would work out of the box.


More information about the mythtv-users mailing list