Re: Getting an Application to work with every remote control

[Paul B. <peb...@gm...>]

On 11/3/2010 4:38 PM, Bastien Nocera wrote:
> On Wed, 2010-11-03 at 23:02 +0000, James Courtier-Dutton wrote:
>> Hi,
>>
>> I would like to be able to have some basic configuration for lircd
>> that will work with my application.
>> I would like to have a .lircrc file that covers every remote control out there.
>> Letting the user only having to select the remote that the application
>> will listen to.
>> To this end, it would be helpful if the "text string" output of irw
>> was similar for all remote control units.
>> An example of the problem.
>> One remote control produces "KEY_PLAYPAUSE" while another produces "PLAYPAUSE".
>> Can there be some standardisation of key names?
>> If so, which of the above two should be used?
>
> gnome-lirc-properties, and the Fedora LIRC packages have scripts (which
> I posted here) to clean up those names.
>
> I hope that I'll have time to run it once more and get it pushed to
> Jarod.
>
> Cheers

My experience from maintaining MiniMyth and eventlircd (eventlircd 
requires the use of the LIRC namespace and is used by MiniMyth) is that 
there are a non-zero number of users that have custom lircd.conf files 
that are not compliant with the LIRC namespace (almost exclusively due 
to RS232 IR receivers). As such, I have begun to think that lirc 0.9.0 
should enforce the LIRC namespace in all LIRC software (with appropriate 
diagnostic output to stderr and/or syslog) unless explicitly overridden 
with a command line option. That way, users that have customized beyond 
what is supported by a distribution's "standard configuration wizards", 
would receive feedback that might enable them to identify and correct 
this problem more quickly.