nospam312 wrote:
>> Remotes aren't keyboards--regardless of what the kernels' input API would
>> have you believe.
>>>> [sorry if I am spelling it out a bit but clearly there is some confusion]
>> Thanks for your reply but my remote has normal TV controls on the
> outside and inside a keyboard. It is a size of a remote control, it
> also controls my TV - it is a remote control.
>> As the device is IR and is a remote control it should be configured
> using LIRC. How else am I going to get an IR remote to work? I even
> included a snippet of my lircrc to show this! LIRC even has support
> for the remote via http://lirc.sourceforge.net/remotes/ as it is a
> remote control.
>> The problem remains it seems that MythTV is converting lowercase
> characters to uppercase characters even though the lircrc config
> binding is set to lowercase characters.
>> I guess I could use the on screen keyboard but then what is the point
> of having the remote control with a keyboard. It would be quicker to
> plug in an actual keyboard than use the on screen keyboard but if you
> have to do that what is the point of having remote control support at
> all.
>>>> If you want your remote treated as a keyboard, then configure it as one, not
>> as a Linux Infrared /Remote/ Control (LIRC) device.
>>>> Aren't "all" LIRC devices treated like keyboards for MythTV use - i.e.
> a remote control button is pressed and that is converted to some
> character key press and then sent to the application?
>> How have you got your remote setup if you are not using LIRC to
> convert your remote button presses to character key presses that are
> then processed by MythTV?
>> The only difference that my remote may have from yours is it has a few
> more buttons that I can map.
>I think this is the same problem that was discussed here a while ago.
http://www.gossamer-threads.com/lists/mythtv/dev/355011#355011
Paul H.