[mythtv-users] different key remappings for different keyboards?
foceni at gmail.com
Tue Feb 9 18:25:28 UTC 2010
On 02/09/2010 05:47 PM, j2u4 j2u4 wrote:
> On Tue, Feb 9, 2010 at 4:40 AM, David Kubicek <foceni at gmail.com
> <mailto:foceni at gmail.com>> wrote:
> On 02/09/2010 01:11 AM, j2u4 j2u4 wrote:
> On 02/08/2010 10:01:54 PM, Michael T. Dean wrote:
> > This is the entire reason LIRC was invented.
> This remote appears as a normal keyboard,* not as an IR device...
> Maybe I don't understand LIRC -- does it control normal usb input
> devices (mouse and keyboard) as well as IR controllers?
> * actually, it appears as two devices, one is a keyboard, and the
> other is a mouse. It's quite the nice little jobber.
> It doesn't by default, but you can route dev/input devices via Lirc
> and some Lirc drivers register their remotes into Linux INPUT
> framework as regular mice/keyboards.
> Usually, this uinput limitation doesn't concern you. It applies
> mostly to BT devices (like my PS3 BD remote), but for those
> remapping is not really required.
> One device appearing as two is normal, all wireless kbd/mouse combos
> do this. The important thing is keyfuzz can remap per device, so
> you're covered.
> Yeah, keyfuzz worked great. Exactly what I was looking for, and super
> easy to set up (with your instructions). Thanks again!
I actually prefer plain INPUT devices, e.g. like remotes supported by
v4l-dvb etc, because it's completely universal. You can also emulate
mouse, but the important thing is all applications can be controlled by
them (no lirc support required) and input focus/sharing is done
automatically by X & WM.
On the other hand, Lirc allows advanced configurations more in line with
the "remote control" concept we're used to from consumer electronics.
Each approach has its perks and disadvantages. I had to switch to Lirc
eventually to be able to implement everything I wanted.
More information about the mythtv-users