Hi! IMHO this mapping should not be defined arbitrarily, but should take exisiting standards into account.
Teletext, MHP, OpenCable, the ATSC DASE standard and others all define "Navigation Keys". See: http://www.mhp.org/mhp_technology/mhp_1_1/ http://www.atsc.org/standards/a100.html http://www.opencable.com/downloads/specs/OC-SP-HOST2.0-I12-070105.pdf For example, OpenCable defines a key "VK_GUIDE" which seems appropriate (see pp. 33). So it should not be a matter of stuffing as many keys as possible into directfb_keyboard.h, but rather mapping "conceptually same" keys to the same values. Regards from Vienna, Richard Unger > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Im Auftrag von Rob Shortt > Gesendet: Mittwoch, 10. Jänner 2007 16:25 > An: directfb-dev > Betreff: [directfb-dev] Adding DIKS_ and DIKI_ defs > > Hi, > > In the process of setting up a new remote controll to use > with the lirc input of DirectFB I am encountering some > missing keys in DirectFB. For example, I would like to map > my GUIDE button to an appropriate key, presumably DIKS_GUIDE, > but no such key exists. > > Is it your desire to populate directfb_keyboard.h (and > directfb_keynames.h) with as many logical key names as > possible? If so then I will be happy to send a patch with my > missing keys. > > Also, is there a special procedure to determine DIKS values > or should I just incriment the value and tag the keys onto > the end of the list? > > Thanks, > -Rob > > _______________________________________________ > directfb-dev mailing list > [email protected] > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
