Dnia 2012-02-27, pon o godzinie 09:55 -0800, Jason Gerecke pisze: [..] > > "Dead" keys are a result of both the block of code you mentioned and > the sendAButton function using the *mapped* button number (instead of > the *physical* button number) as an index into the actions array. When > xsetwacom sets "button 4", its setting the action to be performed when > X11 button 4 is used. Since the block of code above maps no physical > button to X11 button 4, it winds up "dead". Actually, if you can find > a way of changing the priv->buttons array (they exist, but aren't in > common use thankfully) you can make buttons perform the actions you > associated with another button... > > Personally I'd like to see this behavior go away. Skipping buttons 4-7 > is one thing (since it doesn't really make sense to have the tablet > buttons produce scroll events by default), but having them be "dead" > just leads to confusion. The only thing that makes me hesitant is the > fact that it'd break *every* configuration script that sets a button > higher than 3. It'd be annoying for users to fix, but probably not a > huge issue. > > Thoughts? > I think we might wait for Peter and Ping. I'd like to see it go away as well, but hid drive is still far from finished and the behaviour is consistend with usb driver. I might come back to it when hid-wacom is finished.
-- Cheers, Przemo ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
