Le lundi 09 juillet 2007 à 10:59 -0700, [EMAIL PROTECTED] a écrit : > On 7/8/07, Frédéric Crozat <[EMAIL PROTECTED]> wrote:
> > I've also found some slight issues in Mandriva configuration tools with > > this tablet (not supporting pad feature and is misconfiguring the device > > to use in xorg.conf) but no worry for that, I'll bring it to the office > > this week and I'll make sure it will be fixed by our configuration tool > > hacker, so next Mandriva release should support wacom tablet out of the > > box. > > Yes, you need to add pad to xorg.conf file. Our configuration tool hacker spent most of today on fixing Wacom tablets support in both Mandriva installer and configuration tools, so next Mandriva release (2008.0, scheduled for october 2007) should support Wacom tablets out of the box. He also plans to issue a bugfix update for our configuration tool for Mandriva 2007 Spring release (ie the latest stable distribution) really soon. For adding "pad" support to xorg.conf, we decided to add pad section for ALL wacom tablets, since we tested with an old Graphire2 tablet we found in our labs (which doesn't need pad section) and it didn't see to cause any problem to wacom xorg driver. This allows our tools to be much simpler than trying to hardcode a list of models for which pad section is needed. Could you confirm it is ok from your side ? > > I also seem usbmouse is conflicting (when loaded) with wacom kernel > > module (on 2.6.17 kernel), preventing X wacom driver to correctly get > > maximum grid size from the tablet through usb. For now, usbmouse must be > > blacklisted (but I don't really like this hack, since it probably > > prevent usb mouse user to have a working mouse). > > For kernel 2.6.17 and older, you need to update both hid-core.c and > wacom.c. For kernel 2.6.18, no need to worry about hid-core.c any > more. Starting from 2.6.18, we have let HID ignore all Wacom devices. Fortunately, Mandriva kernel for 2007.x distribution has already the hid-core.c from 2.6.18, featuring blacklisting for wacom tablets, so no need to update hid-core.c. After doing more tests, I discovered our usb coldplug support through udev seems to cause usbmouse driver to be loaded before wacom driver. Moreover, I get different behaviours between 2 Mandriva 2007 Spring systems, where one is loading wacom driver first (so it doesn't cause any problem) and the other one is loading usbmouse first. I'll investigate further. > > A sidenote regarding udev rule in howto : %e support has been dropped > > from recent udev release, because it is unreliable. > > I am working on the web pages to include these new changes. We have changed our tools to use a "by-id" path for device name (something like /dev/input/by-id/usb-Wacom_Co.,Ltd._MTE-450-event-mouse ) so configuration file is no longer sensitive to usb input device plug order. This feature (see /etc/udev/rules.d/60-persistent-input.rules) is available in udev since udev version 094 (released about one year ago). It is probably best to advice people to use this kind of path. The only possible issue I can see if somebody plugs two wacom tablets which are exactly the same model (it doesn't seem to be handled by udev). > > Anyway, my real question is about getting this behaviour from touchpad > > on Gimp (ie following Window behaviour): > > -when using circular motion, zoom in / out > > -when pressing up/down (and even better left/right, if possible), > > scrolling up/down (left/right) > > > > ATM, I'm getting the following behaviour : > > -when sliding circular on the touchpad, event for button 4 and 5 are > > sent to X application; > > -when pressing up and down "arrow parts" of the touchpad, no event is > > send. > > > > I'm not really sure how to use xsetwacom to configure this part (I don't > > really understand which parameter should be used for Bamboo). > > Again, I am updating the web pages related to xsetwacom as well. For > users who are running 0.7.8, "xsetwacom -h", "xsetwacom list param", > "xsetwacom list mod" lists current usage, options, and modifiers. To > see what option/parameter an input, such as ring, wheeel, button, is, > please use xidump. > > For your particular case, Bamboo, the touch ring is AbsWUp/AbsWDn and > the tablet buttons are button 1/2/3/4. Here is an example of their > usage: > > xsetwacom set pad AbsWUp "core key pgup" # sending page up event > when moving anti-clockwise > > xsetwacom set pad AbsWDn "core key pgdn" # sending page down event > when mvoing clockwise > > xsetwacom set pad button1 "core key left" > xsetwacom set pad button2 "core key right" > xsetwacom set pad button3 "core key shift alt ctrl" Thanks for your help. But it seems to imply it is not possible to have fast scrolling as advertised in "user manual", from Windows driver ; I'm quoting manual : * Continuous scrolling: Press and hold your finger at the upper end of the Touch Ring to continuously scroll up. Press and hold your finger at the lower end of the Touch Ring to continuously scroll down. * Single step scrolling: Tap your finger on the upper end of the Touch Ring to scroll up one step at a time. Tap your finger on the lower end of the Touch Ring to scroll down one step at a time. Does it mean it is a software only feature, done by Windows driver ? If so, I guess it could be done in xorg driver too (and it seems somehow similar from Stefen Klemer proposal in "Scrolling with Stylus" thread). -- Frédéric Crozat ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Linuxwacom-discuss mailing list Linuxwacom-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
