On Thu, Mar 31, 2011 at 9:28 PM, Peter Hutterer <peter.hutte...@who-t.net> wrote: > On Thu, Mar 31, 2011 at 12:07:32AM -0700, Jason Gerecke wrote: >> On Wed, Mar 30, 2011 at 9:20 PM, Peter Hutterer >> <peter.hutte...@who-t.net> wrote: >> > On Wed, Mar 30, 2011 at 01:54:47PM -0700, Jason Gerecke wrote: >> >> Adding to the only-kinda-hackish use of XGetDeviceButtonMapping, >> >> in get_map, this total hackjob of a patch "fixes" the problem with >> >> us having no way of knowing the driver's defaults for wheels and >> >> strips. >> >> >> >> Thankfully, the defaults aren't changing anytime soon so its >> >> not likely to break. Additionally, once the raw button path is >> >> removed from the driver, the entire 'get_map' function can go >> >> the way of the dodo. >> > >> > This seems to solve the wrong problem. How about we decide that xsetwacom >> > controls the physical buttons on the device? That way, anyone wanting to >> > configure logical mapping can use the X tools and xsetwacom is >> > driver-specific and stays (documented so!) driver-specific. which of course >> > also means we need to check that the Button xorg.conf option does the right >> > thing. >> > >> That would make a number of things easier, but also comes with its own >> drawbacks. I think we should probably figure out where hassle, >> correctness, and compatibility collide first. > > just checked the man page again: > > Option "ButtonM" "AC" > reports an action AC when button M is pressed, where M is one of the > device supported button numbers, it can be 1 to 32. Wacom uses a > driver-internal button mapping, where any physical button appears to the > X server as the button specified by the ButtonM mapping. Hence, if two > physical buttons have the same ButtonM mapping, the server will think > they are the same physical button. The default action reported to the X > server is mouse button M click. Because X uses buttons 4, 5, 6, and 7 as > the four scrolling directions, physical buttons 4 and higher are mapped > to 8 and higher by default. To ignore the button click, i.e., to not > report any button click event to the X server, use "0" or "button 0". > > so at least for the xorg.conf option, we already say that this is the > _physical_ button mapping. I guess it makes sense then to have xsetwacom do > the same on the physical buttons and leave the X specific stuff up to the X > tools. > > Cheers, > Peter > And xsetwacom's man page is wholly silent on just what its version 'M' is, so deferring to the existing docs would make sense.
Of course, despite the lack of official documentation, its "expected" by users familiar with xsetwacom that it use the X button number. Don't get me wrong -- I'd love to see the change. I just hate breaking things for our users/customers without good cause. :) Then again, we already broke compatibility in the last release, so... Jason --- Day xee-nee-svsh duu-'ushtlh-ts'it; nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it. Huu-chan xuu naa~-gha. ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
