Hi!
Uplink "
advantis@..." wrote:
[...]
> Christoph Bartelmus wrote:
>> PS. Let me know if it has already been done, because the closest thing I
>>> could find on Google was some intent on writing a program for generating
>>> lircd.conf settings from Pronto codes.
>>
>> Why didn't you try creating such a converter? Would be much cleaner.
>
> I find such a lircd.conf generator inefficient. I my case, I have a big
> database of pronto codes for different devices and putting all of them
> in lircd.conf would generate a big config file. Then, each time I'd
> learn a new code, I'd have to regenerate lircd.conf. Now, if I were to
> go the lircd.conf generation way, I'd still have to account for a
> noticeable memory usage increase in lircd, right? That's why I made this
> the way I did, so I can send any pronto code I want, whenever I want,
> without reconfiguring and reloading lirc.
It seems that your use case is quite uncommon. Of how many devices are
we talking? 10, 100, 1000? I wouldn't care much about memory usage for
10. 100 should work too. I can't think of a use case where one would
need 1000 devices.
I don't know much about the pronto file format, but LIRC has a method to
store the codes very efficiently, not having to store the pulse sequence
for each key.
Christoph
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
