Dnia 2012-02-29, śro o godzinie 14:36 +1000, Peter Hutterer pisze: [..] > I assume the reason you are confused is because you are working too much > with the kernel and its BTN_4 numbering ;) Hmmm, I can't say "no" :-D > realistically, we cannot get rid of it. button 4-7 for scrolling will stay > with us as long as X is alive. I think the issue here is more one of > documentation than an actual technical issue. even in the default > configuration, a user never sees a button 4 press event (except for > scrolling). so to the user, button 4 is already button 8. > > The best argument I can find is that we're using the logical button mapping > in the driver as opposed to e.g. evdev's physical button mapping in the > driver and that is inconsistent between drivers. Not the only thing > inconsistent though. > > other than that, right now I don't see what benefit it really gives us, > especially for the cost of breaking scripts. > > Plus, if Button 4-7 is dead, it should be easy enough to put out an > xsetwacom warning and refer users to the man page. > OK, that's pretty much EOT. I'll have to live with that ;-) Thanks for the explanation! -- Przemo
------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
