On Mon, Feb 27, 2012 at 5:29 AM, Przemo Firszt <prz...@firszt.eu> wrote: > Dnia 2012-02-27, pon o godzinie 10:54 +0000, Przemo Firszt pisze: >> I'm experiencing some problems with pad buttons. They are not >> overlapping with pen buttons (that's OK), but if I try to redefine them >> using: >> >> xsetwacom --set "Wacom Intuos4 WL pad" Button 1 "key 1" >> >> there is a gap in numbering. Buttons 4 to 7 are "dead" - I mean that despite >> of >> using BTN_4, BTN_5 and so on in the driver, the button "number 4" on >> the pad is mapped to button 8 >> >> The numbering goes like that: 1-2-3-8-9-10-11-12-13 >> >> I presume it's a known issue, but what is the long term plan to solve this? >> >> Chris, you've mentioned some odd behavior of pad buttons, did you mean that >> or >> overlapping the buttons with pen buttons? > > Just in case someone was as confused as me. wcmCommonc has this: > > /* Default button and expresskey values, offset buttons 4 and higher > * by the 4 scroll buttons. */ > for (i=0; i<WCM_MAX_BUTTONS; i++) > priv->button[i] = (i < 3) ? i + 1 : i + 5; > > so buttons 4-5-6-7 are scroll buttons, so numbering of the buttons on > the pad is going to stay a bit ... inconsistent. > > -- > regards, > Przemo >
"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? Jason --- Day xee-nee-svsh duu-'ushtlh-ts'it; nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it. Huu-chan xuu naa~-gha. ------------------------------------------------------------------------------ Try before you buy = See our experts in action! 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-dev2 _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
