[Kde-hardware-devel] Data format for RemoteControl events

[Kevin Ottens]

On Monday 14 September 2009 10:45:05 Michael Zanetti wrote:
> On Saturday 12 September 2009 21:40:57 Christopher Blauvelt wrote:
> > Your caution in creating an enum for every imaginable button is
> > warranted. I can't imagine what LIRC would need over 600 defined buttons
> > for on a remote control.  If you're going to go that way your idea of
> > creating a limited subset of those buttons and having a catch-all
> > (Invalid) to go back to string checking would definitely work.
> 
> Yeah... I think I will go for the limited subset then...

I definitely agree with Christopher here.
 
> > I would change Invalid to be
> > Unknown to keep with the Solid naming convention.
> 
> Exactly what I thought after sending the mail :)

That as well. :-)
 
> > Don't take it as a lack of interest that nobody had answered you.  Kevin
> > typically takes weeks to answer emails :)

And keep in mind that this list is not an alias for ervin at kde.org. ;-)

> My experience with Kevin's RTT is exactly the opposite. But I guess I was
>  just lucky then :)

You were probably lucky. OTOH I improved the RTT lately, so depends if you 
just mail in a period where I'm a blackhole (travelling, etc.)
 
Regards.
-- 
Kévin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le maître sans disciple, Ni le disciple sans maître,
Ne font reculer l'ignorance."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-hardware-devel/attachments/20090915/969ece5c/attachment.sig