Those three buttons are partially implemented. When the 24HD came out last year, the plan was to send KEY_* events from the kernel and have the X driver send keyboard events so that the user could easily bind them to opening help/keyboard/settings (see http://old.nabble.com/Cintiq-24HD-td32593632.html). The kernel part is implemented but the X driver silently ignores the events. It'll take a bit of work to get them to work since we don't have code in place to send keyboard events, but I might be able to add that into my project to support the 24HD touch.
The buttons are different on the 22HD, which brings up a question of how we want to represent things. Should the KEY_* events from the kernel have meaning specific to the hardware (e.g. KEY_PROG1 indicates the "first" hardware control button was pressed), or specific to the button (e.g. KEY_PROG1 indicates a "wrench" button has been pressed)? The former is how ExpressKeys are currently handled, and I believe how Ping's kernel patches are currently coded. On the other hand, since these buttons have semantic meaning (unlike the ExpressKeys) the latter may be desired (though "KEY_PROG1" doesn't really tell you anything... it'd need to be a convention). Tangentially, one of those three buttons on the 22HD is a "list" button that brings up the LCD brightness/contrast/etc. controls. This button is handled 100% by the firmware and the kernel doesn't hear a peep out of it (despite, oddly, it having a spot in the wire protocol). I'm not sure how we want libwacom to describe that particular button... Jason --- Day xee-nee-svsh duu-'ushtlh-ts'it; nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it. Huu-chan xuu naa~-gha. On Mon, Jul 23, 2012 at 1:49 AM, Olivier Fourdan <ofour...@redhat.com> wrote: > Hi all, > > Looking at the pics of recent Cintiq tablets, I see 3 buttons (maybe > more dunno) which look like: > > - an "i" > - a keyboard > - a wrench > > I guess this is used for help, virtual keyboard and access to the > settings panel. > > Do we get events reported for those on Linux? I don't have any such > device so I haven't tested, sorry :-/ > > If so I guess we would need to add semantics for these button in > libwacom, being able to access those would be neat as we could map > directly the similar GNOME functions to these buttons (I am thinking > of the OSD window for the "i" button, screen keyboard for the keyboard > button and Wacom settings panel for the wrench. > > Cheers, > Olivier. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Linuxwacom-devel mailing list > Linuxwacom-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
