digimend-users Mailing List for DIGImend (Page 22)
Brought to you by:
spb_nick
Menu
▾
▴
digimend-users — General discussion and user support
You can subscribe to this list here.
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(58) |
May
(72) |
Jun
(24) |
Jul
|
Aug
(12) |
Sep
(9) |
Oct
(10) |
Nov
(2) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
(5) |
Feb
(23) |
Mar
|
Apr
|
May
(4) |
Jun
(7) |
Jul
(2) |
Aug
(2) |
Sep
(5) |
Oct
(7) |
Nov
(31) |
Dec
(11) |
| 2014 |
Jan
(13) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(12) |
Aug
(10) |
Sep
(13) |
Oct
(15) |
Nov
(49) |
Dec
(4) |
| 2015 |
Jan
(49) |
Feb
(62) |
Mar
(81) |
Apr
(10) |
May
(4) |
Jun
(6) |
Jul
(17) |
Aug
(3) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(8) |
| 2016 |
Jan
(8) |
Feb
(5) |
Mar
(7) |
Apr
(7) |
May
(3) |
Jun
(4) |
Jul
(12) |
Aug
(8) |
Sep
(6) |
Oct
(4) |
Nov
(1) |
Dec
|
|
From: Favux ... <fav...@gm...> - 2012-04-19 01:25:07
|
On Wed, Apr 18, 2012 at 3:54 PM, Nikolai Kondrashov <sp...@gm...> wrote:
>
>> This was suppose to be solved by negative matches being
>> allowed in X Server 1.11, which should allow matching to the parent
>> device/stylus. Don't know if it was, because I haven't investigated
>> this yet. A quick look at 'man xorg.conf.d' doesn't seem to indicate
>> negative matching has been added in X Server 1.11.3.
>
>
> How is this matching supposed to work?
No idea. That's all Peter said, that negative matching would be
available and that would fix it. My guess has been that a new match
or option parameter would be introduced, called say DoNotMatch. So
then with a Wacom graphics tablet with stylus, eraser, cursor, and pad
the stylus snippet would look something like:
MatchDriver "wacom"
DoNotMatch "eraser|cursor|pad"
>> This was a problem for the WizardPen driver also. It could not handle
>> either a mouse or two devices and if the kernel said a mouse was
>> allegedly present the stylus didn't work.
>
>
> Sorry, I'm not sure I understand this.
Sorry, I didn't ever investigate it. I assumed the WizardPen driver
didn't have code to support a mouse. So maybe a Relative/Absolute
Mode conflict? We did try to place the mouse on evdev while keeping
the stylus on WizardPen and that didn't work. Not helped when both
devices had the same name.
>
>> So from my perspective this may be a feature missing from evdev. But
>> not an evdev bug per se.
>
>
> I think I should look into the kernel code and see if I could assign names
> to input devices created from report IDs. Maybe I could assign the suffixes
> to them there.
That might be the cleanest solution if it is doable.
Favux
|
|
From: Nikolai K. <sp...@gm...> - 2012-04-18 20:54:41
|
Hi David, On 04/17/2012 05:48 PM, Favux ... wrote: > The Wacom X driver xf86-input-wacom gets around this issue by > appending the device type (stylus, eraser, cursor, touch, pad) to the > parent (descriptive) device name from the kernel. So in 'xinput list' > you see things like: > ⎜ ↳ Wacom Bamboo 2FG 4x5 Pen stylus id=8 [slave pointer (2)] > ⎜ ↳ Wacom Bamboo 2FG 4x5 Finger touch id=9 [slave pointer (2)] > > ⎜ ↳ Wacom Bamboo 2FG 4x5 Pen eraser id=13 [slave pointer (2)] > ⎜ ↳ Wacom Bamboo 2FG 4x5 Finger pad id=14 [slave pointer (2)] > > Notice for this BambooPT tablet there are two parent devices exported > from the kernel, the 'Wacom Bamboo 2FG 4x5 Pen' and the 'Wacom Bamboo > 2FG 4x5 Finger'. > > This permits identifying specific input tools with snippets in a > custom .conf file in /etc/X11/xorg.conf.d (with X Server 1.10) or in > the xsetwacom run-time commands. > The problem with using the device ID # is that the # can change with a hot > plug so it can't be relied on from session to session. So, this is the problem the GIMP developers are trying to solve. I should've thought about it. I think the only way this could be solved currently, at least to some extent is by matching device name and "type". I'm not sure, though, how much type information is really available to GIMP. It could actually be that the GIMP has started interpreting the absolute mouse of i608X as an extended input device and this leads to confusion when configuring it. > Unfortunately this does create a issue with parent device input tool, > usually the stylus. The X Server makes the MatchProduct match before the > input tools are appended so Options can not be applied to the stylus input > tool separately, instead they are tablet wide. Sure, because the driver is assigned as a result of matching only. > This was suppose to be solved by negative matches being > allowed in X Server 1.11, which should allow matching to the parent > device/stylus. Don't know if it was, because I haven't investigated > this yet. A quick look at 'man xorg.conf.d' doesn't seem to indicate > negative matching has been added in X Server 1.11.3. How is this matching supposed to work? > This was a problem for the WizardPen driver also. It could not handle > either a mouse or two devices and if the kernel said a mouse was > allegedly present the stylus didn't work. Sorry, I'm not sure I understand this. > That's why Martin Owen's > (DoctorMo) wizardpen.conf had a snippet matching to the mouse and > ignoring it. Originally: > Driver " " > Peter Hutterer thought that was quite "original" Apparently using a > null driver was an unanticipated usage. So later changed to the > "conventional": > Option "Ignore" "on" That was an interesting approach, for sure. > So from my perspective this may be a feature missing from evdev. But > not an evdev bug per se. I think I should look into the kernel code and see if I could assign names to input devices created from report IDs. Maybe I could assign the suffixes to them there. Sincerely, Nick |
|
From: Nikolai K. <sp...@gm...> - 2012-04-18 10:10:59
|
On Wed, Apr 18, 2012 at 1:05 PM, Nicodem <nic...@gm...> wrote: > Now with default file its working and wacom applet sees my tablet! > I have finally mapped tablet to second monitor only, thanks! Great! > eraser button is not working, but its not a big problem for me. > i think I will find my way to remap some buttons. This is strange. It should work. Do you see the "eraser" device in "xinput list"? Which application did you test it with and how? > thanks for yours help!!! You're welcome :) Sincerely, Nick |
|
From: Nicodem <nic...@gm...> - 2012-04-18 10:06:00
|
> First of all, AFAIK, you're not supposed to change files under > /usr/share/X11/xorg.conf.d, but instead should add your own under > /etc/X11/xorg.conf.d. I know as it can be overwritten with system update. However I wanted to make changes only here in order to be sure that conf files are used in my configuration. Without yours kernel patch I had to use "Sirius" as Vendor and only then it worked. Now with default file its working and wacom applet sees my tablet! I have finally mapped tablet to second monitor only, thanks! eraser button is not working, but its not a big problem for me. i think I will find my way to remap some buttons. thanks for yours help!!! > Then, the snippet above looks OK. However, just to be sure, could you please > replace /usr/share/X11/xorg.conf.d/50-wacom.conf with the one from the > latest Git version here: > http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/xf86-input-wacom;a=blob_plain;f=conf/50-wacom.conf;hb=HEAD > > Then restart the X server and check the "xinput list" output. > > Sincerely, > Nick |
|
From: Nikolai K. <sp...@gm...> - 2012-04-18 09:31:16
|
On Wed, Apr 18, 2012 at 12:14 PM, Nicodem <nic...@gm...> wrote: > /etc/X11/xorg.conf.d > is empty > > nicodem@nicodem:/usr/share/X11/xorg.conf.d$ cat 50-wacom.conf > # Waltop tablets > Section "InputClass" > Identifier "Waltop class" > MatchProduct "Sirius" > MatchIsTablet "on" > MatchDevicePath "/dev/input/event*" > Driver "wacom" > EndSection First of all, AFAIK, you're not supposed to change files under /usr/share/X11/xorg.conf.d, but instead should add your own under /etc/X11/xorg.conf.d. Then, the snippet above looks OK. However, just to be sure, could you please replace /usr/share/X11/xorg.conf.d/50-wacom.conf with the one from the latest Git version here: http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/xf86-input-wacom;a=blob_plain;f=conf/50-wacom.conf;hb=HEAD Then restart the X server and check the "xinput list" output. Sincerely, Nick |
|
From: Nicodem <nic...@gm...> - 2012-04-18 09:14:55
|
/etc/X11/xorg.conf.d
is empty
in usr:
nicodem@nicodem:/usr/share/X11/xorg.conf.d$ ls -all
razem 36
drwxr-xr-x 2 root root 4096 kwi 18 11:13 .
drwxr-xr-x 5 root root 4096 kwi 5 10:42 ..
-rw-r--r-- 1 root root 1099 kwi 5 02:04 10-evdev.conf
-rw-r--r-- 1 root root 590 mar 15 16:52 11-evdev-quirks.conf
-rw-r--r-- 1 root root 364 mar 15 16:52 11-evdev-trackpoint.conf
-rw-r--r-- 1 root root 956 kwi 13 15:00 50-synaptics.conf
-rw-r--r-- 1 root root 115 mar 22 17:54 50-vmmouse.conf
-rw-r--r-- 1 root root 686 kwi 16 14:57 50-wacom.conf
-rw-r--r-- 1 root root 590 kwi 13 14:59 51-synaptics-quirks.conf
and 50-wacom.conf:
nicodem@nicodem:/usr/share/X11/xorg.conf.d$ cat 50-wacom.conf
# Waltop tablets
Section "InputClass"
Identifier "Waltop class"
MatchProduct "Sirius"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
EndSection
Section "InputClass"
Identifier "Wacom serial class"
MatchProduct "Serial Wacom Tablet"
Driver "wacom"
EndSection
Section "InputClass"
Identifier "Wacom serial class identifiers"
MatchProduct "WACf|FUJ02e5|FUJ02e7"
Driver "wacom"
EndSection
# N-Trig Duosense Electromagneti c Digitizer
Section "InputClass"
Identifier "Wacom N-Trig class"
MatchProduct "HID 1b96:0001|N-Trig Pen"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
Option "Button2" "3"
EndSection
On Wed, Apr 18, 2012 at 11:09 AM, Nikolai Kondrashov <sp...@gm...> wrote:
> On Wed, Apr 18, 2012 at 11:55 AM, Nicodem <nic...@gm...> wrote:
>> Thanks for explanation. New kernel installed and running.
>> I got button for sub-menu working!!!
>> still wacom app does not see my tablet so I cannot configure it for
>> one monitor only. This would be great as with current cofiguration:
>> laptop disp - 1366x768, second monitor 1920x1080 I have eggs not circles :)
>> I must turn of monitor and work at the one only to have proper proportions.
>>
>> here is my current config:
>
> The pen input is still being handled by evdev. This manifests as only one
> pointer device (wacom driver would make two - stylus and eraser) and the
> presense of properties with "Evdev" prefix for the pointer device.
>
> Please check the X.org configuration. If you can't find the problem, please
> post all the files from your /etc/X11/xorg.conf.d directory here. Please
> also post /usr/share/X11/xorg.conf.d/50-wacom.conf.
>
> Thanks.
>
> Sincerely,
> Nick
|
|
From: Nikolai K. <sp...@gm...> - 2012-04-18 09:09:33
|
On Wed, Apr 18, 2012 at 11:55 AM, Nicodem <nic...@gm...> wrote: > Thanks for explanation. New kernel installed and running. > I got button for sub-menu working!!! > still wacom app does not see my tablet so I cannot configure it for > one monitor only. This would be great as with current cofiguration: > laptop disp - 1366x768, second monitor 1920x1080 I have eggs not circles :) > I must turn of monitor and work at the one only to have proper proportions. > > here is my current config: The pen input is still being handled by evdev. This manifests as only one pointer device (wacom driver would make two - stylus and eraser) and the presense of properties with "Evdev" prefix for the pointer device. Please check the X.org configuration. If you can't find the problem, please post all the files from your /etc/X11/xorg.conf.d directory here. Please also post /usr/share/X11/xorg.conf.d/50-wacom.conf. Thanks. Sincerely, Nick |
|
From: Nicodem <nic...@gm...> - 2012-04-18 08:55:58
|
Thanks for explanation. New kernel installed and running.
I got button for sub-menu working!!!
still wacom app does not see my tablet so I cannot configure it for
one monitor only. This would be great as with current cofiguration:
laptop disp - 1366x768, second monitor 1920x1080 I have eggs not circles :)
I must turn of monitor and work at the one only to have proper proportions.
here is my current config:
nicodem@nicodem:~$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ USB OPTICAL MOUSE id=11 [slave pointer (2)]
⎜ ↳ Logitech Unifying Device. Wireless PID:200a id=12 [slave pointer (2)]
⎜ ↳ WALTOP Batteryless Tablet id=15 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=17 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sony Vaio Keys id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ UVC Camera (05ca:18b7) id=10 [slave keyboard (3)]
↳ WALTOP Batteryless Tablet id=13 [slave keyboard (3)]
↳ WALTOP Batteryless Tablet id=14 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)]
nicodem@nicodem:~$ xinput list-props 15
Device ' WALTOP Batteryless Tablet ':
Device Enabled (131): 1
Coordinate Transformation Matrix (133): 1.000000, 0.000000, 0.000000,
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (258): 0
Device Accel Constant Deceleration (259): 1.000000
Device Accel Adaptive Deceleration (260): 1.000000
Device Accel Velocity Scaling (261): 10.000000
Device Product ID (250): 5935, 1282
Device Node (251): "/dev/input/event9"
Evdev Axis Inversion (262): 0, 0
Evdev Axis Calibration (263): 0, 20000, 0, 12000
Evdev Axes Swap (264): 0
Axis Labels (265): "Abs X" (280), "Abs Y" (281), "Abs Pressure"
(282), "Abs Tilt X" (283), "Abs Tilt Y" (284)
Button Labels (266): "Button Unknown" (253), "Button Unknown" (253),
"Button Unknown" (253), "Button Wheel Up" (137), "Button Wheel Down"
(138), "Button Horiz Wheel Left" (139), "Button Horiz Wheel Right"
(140)
Evdev Middle Button Emulation (267): 0
Evdev Middle Button Timeout (268): 50
Evdev Third Button Emulation (269): 0
Evdev Third Button Emulation Timeout (270): 1000
Evdev Third Button Emulation Button (271): 3
Evdev Third Button Emulation Threshold (272): 20
Evdev Wheel Emulation (273): 0
Evdev Wheel Emulation Axes (274): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (275): 10
Evdev Wheel Emulation Timeout (276): 200
Evdev Wheel Emulation Button (277): 4
Evdev Drag Lock Buttons (278): 0
nicodem@nicodem:~$
nicodem@nicodem:~$ xinput list-props 13
Device ' WALTOP Batteryless Tablet ':
Device Enabled (131): 1
Coordinate Transformation Matrix (133): 1.000000, 0.000000, 0.000000,
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Product ID (250): 5935, 1282
Device Node (251): "/dev/input/event11"
nicodem@nicodem:~$
nicodem@nicodem:~$ xinput list-props 14
Device ' WALTOP Batteryless Tablet ':
Device Enabled (131): 1
Coordinate Transformation Matrix (133): 1.000000, 0.000000, 0.000000,
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Product ID (250): 5935, 1282
Device Node (251): "/dev/input/event12"
nicodem@nicodem:~$
|
|
From: Nikolai K. <sp...@gm...> - 2012-04-18 08:12:51
|
On Wed, Apr 18, 2012 at 11:05 AM, Nicodem <nic...@gm...> wrote: >> First of all, please try one of the kernels I've released yesterday. >> This set of packages is the one you requested: >> https://sourceforge.net/projects/digimend/files/kernel-packages/kernel-patches-5/ubuntu_12.04_i386/ > > Thanks! > OK, now comes hard part - how can I use this new kernel? I have never > udated kernel by myself. Is there any how-to for it? No, there is no HOWTO for now, but I did a blog post explaining some of it: https://sourceforge.net/apps/wordpress/digimend/2012/04/17/first-kernel-packages-are-out/ Please download and install these files in this order: http://sourceforge.net/projects/digimend/files/kernel-packages/kernel-patches-5/ubuntu_12.04_i386/linux-image-3.2.0-23-generic-pae-digimend_3.2.0-23.36%2Bdigimend.5.1_i386.deb/download http://sourceforge.net/projects/digimend/files/kernel-packages/kernel-patches-5/ubuntu_12.04_i386/linux-headers-3.2.0-23_3.2.0-23.36%2Bdigimend.5.1_all.deb/download http://sourceforge.net/projects/digimend/files/kernel-packages/kernel-patches-5/ubuntu_12.04_i386/linux-headers-3.2.0-23-generic-pae-digimend_3.2.0-23.36%2Bdigimend.5.1_i386.deb/download Most likely you will be able to install them just by double-clicking in your file manager or from you browser download prompt. Otherwise, you can always install them using "sudo dpkg -i" from the console. After that you will be able to reboot into the new kernel. Sincerely, Nick |
|
From: Nicodem <nic...@gm...> - 2012-04-18 08:05:13
|
> First of all, please try one of the kernels I've released yesterday. > This set of packages is the one you requested: > https://sourceforge.net/projects/digimend/files/kernel-packages/kernel-patches-5/ubuntu_12.04_i386/ Thanks! OK, now comes hard part - how can I use this new kernel? I have never udated kernel by myself. Is there any how-to for it? |
|
From: Nikolai K. <sp...@gm...> - 2012-04-18 07:47:58
|
Hi Dominik, First of all, please try one of the kernels I've released yesterday. This set of packages is the one you requested: https://sourceforge.net/projects/digimend/files/kernel-packages/kernel-patches-5/ubuntu_12.04_i386/ On 04/16/2012 03:49 PM, Nicodem wrote: > > > > Yes. The output shows that you're using the xf86-input-evdev driver. > > how can I change it to wacom? You don't necessarily need to, but it should be enough just to install the wacom X driver with the default configuration. Please note, that currently the tablet only works with 2000 LPI resolution and horizontal scrolling doesn't work. With evdev tilt will work in most applications, but not the eraser button. With the wacom driver it's the other way around for now. Although the eraser button would probably never work with evdev, I'm trying to make the tilt work with the wacom driver. > 50-wacom.conf file wasnt working with me is such config: > # Waltop tablets > Section "InputClass" > Identifier "Waltop class" > MatchProduct "WALTOP" > MatchIsTablet "on" > MatchDevicePath "/dev/input/event*" > Driver "wacom" > EndSection This snippet should work with our kernel. > any ideas? > should I dump anything more here what would be helpful ? No, please try the released kernel first. Thanks. Sincerely, Nick |
|
From: Favux ... <fav...@gm...> - 2012-04-17 14:55:45
|
Hi, The Wacom X driver xf86-input-wacom gets around this issue by appending the device type (stylus, eraser, cursor, touch, pad) to the parent (descriptive) device name from the kernel. So in 'xinput list' you see things like: ⎜ ↳ Wacom Bamboo 2FG 4x5 Pen stylus id=8 [slave pointer (2)] ⎜ ↳ Wacom Bamboo 2FG 4x5 Finger touch id=9 [slave pointer (2)] ⎜ ↳ Wacom Bamboo 2FG 4x5 Pen eraser id=13 [slave pointer (2)] ⎜ ↳ Wacom Bamboo 2FG 4x5 Finger pad id=14 [slave pointer (2)] Notice for this BambooPT tablet there are two parent devices exported from the kernel, the 'Wacom Bamboo 2FG 4x5 Pen' and the 'Wacom Bamboo 2FG 4x5 Finger'. This permits identifying specific input tools with snippets in a custom .conf file in /etc/X11/xorg.conf.d (with X Server 1.10) or in the xsetwacom run-time commands. The problem with using the device ID # is that the # can change with a hot plug so it can't be relied on from session to session. Unfortunately this does create a issue with parent device input tool, usually the stylus. The X Server makes the MatchProduct match before the input tools are appended so Options can not be applied to the stylus input tool separately, instead they are tablet wide. This was suppose to be solved by negative matches being allowed in X Server 1.11, which should allow matching to the parent device/stylus. Don't know if it was, because I haven't investigated this yet. A quick look at 'man xorg.conf.d' doesn't seem to indicate negative matching has been added in X Server 1.11.3. This was a problem for the WizardPen driver also. It could not handle either a mouse or two devices and if the kernel said a mouse was allegedly present the stylus didn't work. That's why Martin Owen's (DoctorMo) wizardpen.conf had a snippet matching to the mouse and ignoring it. Originally: Driver " " Peter Hutterer thought that was quite "original" Apparently using a null driver was an unanticipated usage. So later changed to the "conventional": Option "Ignore" "on" So from my perspective this may be a feature missing from evdev. But not an evdev bug per se. Favux |
|
From: Nikolai K. <sp...@gm...> - 2012-04-17 13:49:02
|
On Tue, Apr 17, 2012 at 4:44 PM, Viktoria S. <vik...@fr...> wrote: > I have filed a bug in gimp for the issue with the Genius MousePen i608X. You can find it here: > https://bugzilla.gnome.org/show_bug.cgi?id=674253 Thank you, Viktoria! I'll keep track of it. Sincerely, Nick |
|
From: Viktoria S. <vik...@fr...> - 2012-04-17 13:44:31
|
Hi! I have filed a bug in gimp for the issue with the Genius MousePen i608X. You can find it here: https://bugzilla.gnome.org/show_bug.cgi?id=674253 Regards: Viktoria |
|
From: Nikolai K. <sp...@gm...> - 2012-04-17 10:25:18
|
Hi Viktoria, Thank you for the detailed analysis and description. On Tue, Apr 17, 2012 at 1:08 PM, Viktoria S. <vik...@fr...> wrote: > So my question is: can we accept the kernel/evdev driver to provide unique > name for the devices or not? > > Because if the device names are not required to be unique: there is bug in > gimp because they should use the device name and the device type as a key > in their device collection. And in that case I guess I'd better file a bug > in gimp. > But on the other hand: if the device names has to be unique, then there is > a bug in the kernel/evdev driver. And in this case I would like to report > a bug to Nick :-) I would say that it's a bug in GIMP and it should be reported to the developers ASAP, before the final 2.8 is released. They may have tried to solve some problem with this approach, but it created another one. Because, the device name is supposed to be descriptive and the only proper device ID is the X input device ID. The one seen in the "xinput list" output. There are at least several other tablets and other input devices, which create several input devices with identical name. Look for HID_QUIRK_MULTI_INPUT in the kernel's drivers/hid/usbhid/hid-quirks.c. Then there are always devices with multiple interfaces and I guess they will get identical names too. While it might be good to add some identification to their names, it shouldn't be required. If you decide to report the bug, could you please post a link to it on DIGImend-users? Thanks. Sincerely, Nick |
|
From: Viktoria S. <vik...@fr...> - 2012-04-17 10:08:42
|
Hi Nick and everybody! I have problem with Genius MousePen i608X driver and using it in Gimp 2.8RC1. The problem seems to be that in this model the name the pen and the mouse are the same. Usually if I have the mousepen plugged in during boot the first item is the pen and the second is the mouse, but if I plug the mousepen after boot the first item will be the mouse and the second will be the pen. I have compiled Gimp 2.8RC1 for myself and I get only one Genius MousePen i608X on the list. As you can see the screenshot in this post: http://ubuntuforums.org/showpost.php?p=11690680&postcount=30. I tried to figure out what can be the problem, since the earlier version of gimp does not have this issue (I have 2 Genius MousePen i608X there to choose from)(Nick earlier thought that the problem could be because the mouse works in absolute mode, but the absolute mouse works perfectly in earlier version of gimp so I thought probably that is not the issue.) So I browsed the code and I have found the code which is creating the device list of the panel: it is in gimp-2.8.0-RC1/app/widgets/gimpdevicemanager.c. In line 313 there is a function gimp_device_manager_device_added. static void gimp_device_manager_device_added (GdkDisplay *gdk_display, GdkDevice *device, GimpDeviceManager *manager) { GimpDeviceManagerPrivate *private = GET_PRIVATE (manager); GimpDeviceInfo *device_info; device_info = GIMP_DEVICE_INFO (gimp_container_get_child_by_name (GIMP_CONTAINER (manager), device->name)); /*if (device_info) { gimp_device_info_set_device (device_info, device, gdk_display); } else {*/ device_info = gimp_device_info_new (private->gimp, device, gdk_display); gimp_container_add (GIMP_CONTAINER (manager), GIMP_OBJECT (device_info)); g_object_unref (device_info); //} } The original code is without comments, and unfortunately it uses the name of the device as a key in a collection to identify the device. If I compile gimp with commented lines all of the devices appear on the list. But there are issues with this: - if I plugin the mousepen after bootup with the original gimp code only the mouse appears on the list, because, as I mentioned in that case the mouse will be the first item in xinput list not the pen. So in this scenario the pen can only be configured with the modified code. - if I were to configure both the mouse and the pen they are going to share the same settings (according color, brush etc.) somehow, I guess because the device name used as a key (In earlier version of the gimp the whole device handling code is different, so there are no such issues. If I configure to use both the pen and the mouse they are going to have defferent brush, color etc. settings.) So my question is: can we accept the kernel/evdev driver to provide unique name for the devices or not? Because if the device names are not required to be unique: there is bug in gimp because they should use the device name and the device type as a key in their device collection. And in that case I guess I'd better file a bug in gimp. But on the other hand: if the device names has to be unique, then there is a bug in the kernel/evdev driver. And in this case I would like to report a bug to Nick :-) Can somebody help with this? Thank you and regards: Viktoria S. |
|
From: Nicodem <nic...@gm...> - 2012-04-16 12:49:17
|
>
> Yes. The output shows that you're using the xf86-input-evdev driver.
how can I change it to wacom?
*lsusb*
Bus 007 Device 002: ID 172f:0502 Waltop International Corp. Sirius Battery
Free Tablet
*xinput list*
nicodem@nicodem:~$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ USB OPTICAL MOUSE id=11 [slave pointer (2)]
⎜ ↳ WALTOP Batteryless Tablet id=12 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)]
⎜ ↳ Logitech Unifying Device. Wireless PID:200a id=15 [slave pointer
(2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sony Vaio Keys id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ UVC Camera (05ca:18b7) id=10 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
50-wacom.conf file wasnt working with me is such config:
# Waltop tablets
Section "InputClass"
Identifier "Waltop class"
MatchProduct "WALTOP"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
EndSection
with such configuration there was no response at all. Tablet was not
working - even not moving pointer.
I have added /etc/X11/xorg.conf.d/52-waltop-on-wacom.conf file:
Section "InputClass"
Identifier "Waltop custom class"
MatchProduct "Sirius"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
Option "Button2" "2"
Option "Button3" "3"
Option "Keepshape" "on"
# Apply custom Options below.
EndSection
and after this my tablet is responsive. Still got some issue but at least
it works as described last time.
I have driver "wacom" set but seems that its working with evdev.
any ideas?
should I dump anything more here what would be helpful ?
Dominik
|
|
From: Nikolai K. <sp...@gm...> - 2012-04-16 12:34:43
|
On Mon, Apr 16, 2012 at 3:21 PM, Nicodem <nic...@gm...> wrote: > what I just found out is that with xinput I got such reponse as below. > Is it possible then that Im using evdev driver, not wacom? Yes. The output shows that you're using the xf86-input-evdev driver. Sincerely, Nick |
|
From: Nikolai K. <sp...@gm...> - 2012-04-16 12:33:03
|
Hi Dominik, Please keep DIGImend-users in the CC by using "Reply to all", instead of "Reply". On Mon, Apr 16, 2012 at 3:00 PM, Nicodem <nic...@gm...> wrote: > currently I got it working under Ubuntu after some deep research with > uncle Google :) Good! > As im using two monitors I still got some issues. Could you please describe them? > And also - now I cannot see device under wacom application - is it > normal? This is something stange as I thought that once it starts > working it should be customizable with wacom app. This is probably because xf86-input-evdev is handling the tablet. > So I still need to resovle buttons issue (all buttons works now as > left-click), proper calibration for two monitors, later additional > buttons (panel left, panel right). This should be resolved by our kernel drivers, included into the kernel packages I'm building. Sincerely, Nick |
|
From: Nikolai K. <sp...@gm...> - 2012-04-16 11:36:42
|
Hi Dominik, On Mon, Apr 16, 2012 at 9:11 AM, Nicodem <nic...@gm...> wrote: > I got Pentagram Designer P 2700 tablet which I cannot use now. Its not > working out of the box with any Ubuntu release I treid (11.10 and > 12.04 LTS). My installed version nor the liveusb. > device is found in lsusb as: > Bus 007 Device 002: ID 172f:0502 Waltop International Corp. Sirius > Battery Free Tablet > > but I cannot even move pointer. Nothing happens. This is somewhat strange, you should've been able to at least move the pointer. Did you check if the tablet works under Windows? I'm in the process of building a set of Ubuntu kernels which should better support your tablet, right now. You could subscribe to the project blog or just visit it to know when they're put out: https://sourceforge.net/apps/wordpress/digimend/ Sincerely, Nick |
|
From: Nicodem <nic...@gm...> - 2012-04-16 06:11:20
|
Hi I got Pentagram Designer P 2700 tablet which I cannot use now. Its not working out of the box with any Ubuntu release I treid (11.10 and 12.04 LTS). My installed version nor the liveusb. device is found in lsusb as: Bus 007 Device 002: ID 172f:0502 Waltop International Corp. Sirius Battery Free Tablet but I cannot even move pointer. Nothing happens. Please help how to get it working? D. |
|
From: Nikolai K. <sp...@gm...> - 2012-04-15 13:06:29
|
Hi Zauber, On Thu, Apr 12, 2012 at 5:09 PM, Zauber Paracelsus <zau...@gm...> wrote: > Above, you'll notice a couple of lines do not report an ABS_X value, so perhaps the driver is interpreting that to mean ABS_X has a value of zero, rather than no change? I see that the tablet itself doesn't jump, so it must be either xf85-input-evdev or X server issue, with the former being much more likely. Yes, it can be the issue, but I'll have to verify that. However, I'm not sure when I'll be able to do that. Hopefully, next week. Also, another user has reported the issue with similar setup and another UC-Logic tablet (WP5540U). > Also, this tablet is a UC-LOGIC WP8060U as mentioned above, sold under the Monoprice brand, in particular this one: https://www.monoprice.com/products/product.asp?c_id=108&cp_id=10841&cs_id=1084101&p_id=5553&seq=1&format=2 Thanks, I have added it to the tablet info: https://sourceforge.net/apps/mediawiki/digimend/index.php?title=UC-Logic_Tablet_WP8060U Sincerely, Nick |
|
From: Zauber P. <zau...@gm...> - 2012-04-12 14:13:10
|
>
> This might be an xf86-input-evdev issue. Still, let's check that it's
> getting correct data.
>
> Once the issue is showing well again, could you please try capturing
> "sudo evtest" output for your tablet, while you move the pen inside a
> small area within the center of the tablet (so that jumps could be
> more obvious)?
>
> If evtest complains that it can't grab the device, please switch to a
> text console and execute "sudo evtest" there.
>
> Evtest will show you two devices for your tablet - one for the pen,
> one for the mouse you don't have. The mouse device will produce no
> output when moving the pen, please run evtest with the other one.
>
> Please send me the output. If it shows no jumps, then I'll try to
> reproduce the issue and will look into the xf86-input-evdev source.
> Otherwise, we will try to check if it's a hardware issue.
>
> BTW, under which name was your tablet sold?
>
> Thank you.
>
> Sincerely,
> Nick
Alright, sorry for the delay in replying. I had trouble finding the tablet in question up until this morning.
Here's the head output of evtest:
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x5543 product 0x5 version 0x100
Input device name: "UC-LOGIC Tablet WP8060U"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 330 (BTN_TOUCH)
Event code 331 (BTN_STYLUS)
Event code 332 (BTN_STYLUS2)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 16976
Min 0
Max 32767
Resolution 161
Event code 1 (ABS_Y)
Value 9597
Min 0
Max 32767
Resolution 215
Event code 24 (ABS_PRESSURE)
Value 0
Min 0
Max 1023
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Testing ... (interrupt to exit)
Event: time 1334239142.335211, type 3 (EV_ABS), code 0 (ABS_X), value 18067
Event: time 1334239142.335216, type 3 (EV_ABS), code 1 (ABS_Y), value 23009
Event: time 1334239142.335220, -------------- SYN_REPORT ------------
Event: time 1334239142.351212, type 3 (EV_ABS), code 0 (ABS_X), value 18014
Event: time 1334239142.351217, type 3 (EV_ABS), code 1 (ABS_Y), value 22851
Event: time 1334239142.351222, -------------- SYN_REPORT ------------
Event: time 1334239142.359199, type 3 (EV_ABS), code 0 (ABS_X), value 18020
Event: time 1334239142.359203, type 3 (EV_ABS), code 1 (ABS_Y), value 22712
Event: time 1334239142.359208, -------------- SYN_REPORT ------------
Event: time 1334239142.367176, type 3 (EV_ABS), code 0 (ABS_X), value 18018
Event: time 1334239142.367180, type 3 (EV_ABS), code 1 (ABS_Y), value 22583
Event: time 1334239142.367185, -------------- SYN_REPORT ------------
Event: time 1334239142.375179, type 3 (EV_ABS), code 0 (ABS_X), value 18035
Event: time 1334239142.375183, type 3 (EV_ABS), code 1 (ABS_Y), value 22438
Event: time 1334239142.375187, -------------- SYN_REPORT ------------
Event: time 1334239142.383218, type 3 (EV_ABS), code 0 (ABS_X), value 18049
Event: time 1334239142.383222, type 3 (EV_ABS), code 1 (ABS_Y), value 22283
Event: time 1334239142.383226, -------------- SYN_REPORT ------------
Event: time 1334239142.391220, type 3 (EV_ABS), code 0 (ABS_X), value 18071
Event: time 1334239142.391224, type 3 (EV_ABS), code 1 (ABS_Y), value 22114
Event: time 1334239142.391228, -------------- SYN_REPORT ------------
Event: time 1334239142.399192, type 3 (EV_ABS), code 0 (ABS_X), value 18108
Event: time 1334239142.399196, type 3 (EV_ABS), code 1 (ABS_Y), value 21955
Event: time 1334239142.399201, -------------- SYN_REPORT ------------
Event: time 1334239142.407217, type 3 (EV_ABS), code 0 (ABS_X), value 18131
Event: time 1334239142.407221, type 3 (EV_ABS), code 1 (ABS_Y), value 21786
Event: time 1334239142.407225, -------------- SYN_REPORT ------------
Event: time 1334239142.415228, type 3 (EV_ABS), code 0 (ABS_X), value 18157
Event: time 1334239142.415232, type 3 (EV_ABS), code 1 (ABS_Y), value 21619
Event: time 1334239142.415237, -------------- SYN_REPORT ------------
Event: time 1334239142.423210, type 3 (EV_ABS), code 0 (ABS_X), value 18166
Event: time 1334239142.423214, type 3 (EV_ABS), code 1 (ABS_Y), value 21458
Event: time 1334239142.423218, -------------- SYN_REPORT ------------
Event: time 1334239142.431208, type 3 (EV_ABS), code 0 (ABS_X), value 18170
Event: time 1334239142.431212, type 3 (EV_ABS), code 1 (ABS_Y), value 21292
Event: time 1334239142.431216, -------------- SYN_REPORT ------------
Event: time 1334239142.439238, type 3 (EV_ABS), code 0 (ABS_X), value 18161
Event: time 1334239142.439241, type 3 (EV_ABS), code 1 (ABS_Y), value 21142
Event: time 1334239142.439245, -------------- SYN_REPORT ------------
Event: time 1334239142.447213, type 3 (EV_ABS), code 0 (ABS_X), value 18147
Event: time 1334239142.447217, type 3 (EV_ABS), code 1 (ABS_Y), value 20989
Event: time 1334239142.447221, -------------- SYN_REPORT ------------
Event: time 1334239142.455227, type 3 (EV_ABS), code 0 (ABS_X), value 18141
Event: time 1334239142.455231, type 3 (EV_ABS), code 1 (ABS_Y), value 20828
Event: time 1334239142.455235, -------------- SYN_REPORT ------------
Event: time 1334239142.463231, type 3 (EV_ABS), code 0 (ABS_X), value 18118
Event: time 1334239142.463235, type 3 (EV_ABS), code 1 (ABS_Y), value 20666
Event: time 1334239142.463240, -------------- SYN_REPORT ------------
Event: time 1334239142.471228, type 3 (EV_ABS), code 0 (ABS_X), value 18102
Event: time 1334239142.471230, type 3 (EV_ABS), code 1 (ABS_Y), value 20486
Event: time 1334239142.471231, -------------- SYN_REPORT ------------
Event: time 1334239142.479206, type 3 (EV_ABS), code 0 (ABS_X), value 18088
Event: time 1334239142.479207, type 3 (EV_ABS), code 1 (ABS_Y), value 20295
Event: time 1334239142.479208, -------------- SYN_REPORT ------------
Event: time 1334239142.487208, type 3 (EV_ABS), code 0 (ABS_X), value 18071
Event: time 1334239142.487209, type 3 (EV_ABS), code 1 (ABS_Y), value 20090
Event: time 1334239142.487210, -------------- SYN_REPORT ------------
Event: time 1334239142.495215, type 3 (EV_ABS), code 0 (ABS_X), value 18059
Event: time 1334239142.495217, type 3 (EV_ABS), code 1 (ABS_Y), value 19877
Event: time 1334239142.495218, -------------- SYN_REPORT ------------
Event: time 1334239142.503218, type 3 (EV_ABS), code 0 (ABS_X), value 18043
Event: time 1334239142.503219, type 3 (EV_ABS), code 1 (ABS_Y), value 19645
Event: time 1334239142.503221, -------------- SYN_REPORT ------------
Event: time 1334239142.511225, type 3 (EV_ABS), code 0 (ABS_X), value 18030
Event: time 1334239142.511227, type 3 (EV_ABS), code 1 (ABS_Y), value 19394
Event: time 1334239142.511228, -------------- SYN_REPORT ------------
Event: time 1334239142.519225, type 3 (EV_ABS), code 0 (ABS_X), value 18020
Event: time 1334239142.519227, type 3 (EV_ABS), code 1 (ABS_Y), value 19132
Event: time 1334239142.519228, -------------- SYN_REPORT ------------
Event: time 1334239142.527239, type 3 (EV_ABS), code 0 (ABS_X), value 18004
Event: time 1334239142.527241, type 3 (EV_ABS), code 1 (ABS_Y), value 18870
Event: time 1334239142.527243, -------------- SYN_REPORT ------------
Event: time 1334239142.535273, type 3 (EV_ABS), code 0 (ABS_X), value 17981
Event: time 1334239142.535277, type 3 (EV_ABS), code 1 (ABS_Y), value 18613
Event: time 1334239142.535282, -------------- SYN_REPORT ------------
Event: time 1334239142.543269, type 3 (EV_ABS), code 0 (ABS_X), value 17953
Event: time 1334239142.543273, type 3 (EV_ABS), code 1 (ABS_Y), value 18335
Event: time 1334239142.543277, -------------- SYN_REPORT ------------
Event: time 1334239142.551263, type 3 (EV_ABS), code 0 (ABS_X), value 17918
Event: time 1334239142.551267, type 3 (EV_ABS), code 1 (ABS_Y), value 18048
Event: time 1334239142.551271, -------------- SYN_REPORT ------------
Event: time 1334239142.559267, type 3 (EV_ABS), code 0 (ABS_X), value 17885
Event: time 1334239142.559271, type 3 (EV_ABS), code 1 (ABS_Y), value 17748
Event: time 1334239142.559275, -------------- SYN_REPORT ------------
Event: time 1334239142.567296, type 3 (EV_ABS), code 0 (ABS_X), value 17852
Event: time 1334239142.567300, type 3 (EV_ABS), code 1 (ABS_Y), value 17444
Event: time 1334239142.567304, -------------- SYN_REPORT ------------
Event: time 1334239142.575255, type 3 (EV_ABS), code 0 (ABS_X), value 17822
Event: time 1334239142.575256, type 3 (EV_ABS), code 1 (ABS_Y), value 17111
Event: time 1334239142.575257, -------------- SYN_REPORT ------------
Event: time 1334239142.583289, type 3 (EV_ABS), code 0 (ABS_X), value 17799
Event: time 1334239142.583293, type 3 (EV_ABS), code 1 (ABS_Y), value 16745
Event: time 1334239142.583297, -------------- SYN_REPORT ------------
Event: time 1334239142.591310, type 3 (EV_ABS), code 0 (ABS_X), value 17781
Event: time 1334239142.591314, type 3 (EV_ABS), code 1 (ABS_Y), value 16344
Event: time 1334239142.591319, -------------- SYN_REPORT ------------
Event: time 1334239142.599295, type 3 (EV_ABS), code 0 (ABS_X), value 17766
Event: time 1334239142.599297, type 3 (EV_ABS), code 1 (ABS_Y), value 15910
Event: time 1334239142.599298, -------------- SYN_REPORT ------------
Event: time 1334239142.607289, type 3 (EV_ABS), code 0 (ABS_X), value 17750
Event: time 1334239142.607293, type 3 (EV_ABS), code 1 (ABS_Y), value 15479
Event: time 1334239142.607297, -------------- SYN_REPORT ------------
Event: time 1334239142.615302, type 3 (EV_ABS), code 0 (ABS_X), value 17744
Event: time 1334239142.615306, type 3 (EV_ABS), code 1 (ABS_Y), value 15058
Event: time 1334239142.615310, -------------- SYN_REPORT ------------
Event: time 1334239142.623322, type 3 (EV_ABS), code 0 (ABS_X), value 17750
Event: time 1334239142.623326, type 3 (EV_ABS), code 1 (ABS_Y), value 14621
Event: time 1334239142.623330, -------------- SYN_REPORT ------------
Event: time 1334239142.631299, type 3 (EV_ABS), code 0 (ABS_X), value 17758
Event: time 1334239142.631303, type 3 (EV_ABS), code 1 (ABS_Y), value 14176
Event: time 1334239142.631307, -------------- SYN_REPORT ------------
Event: time 1334239142.639311, type 3 (EV_ABS), code 1 (ABS_Y), value 13726
Event: time 1334239142.639316, -------------- SYN_REPORT ------------
Event: time 1334239142.647338, type 3 (EV_ABS), code 0 (ABS_X), value 17764
Event: time 1334239142.647343, type 3 (EV_ABS), code 1 (ABS_Y), value 13281
Event: time 1334239142.647347, -------------- SYN_REPORT ------------
Event: time 1334239142.655347, type 3 (EV_ABS), code 1 (ABS_Y), value 12844
Event: time 1334239142.655353, -------------- SYN_REPORT ------------
Event: time 1334239142.663352, type 3 (EV_ABS), code 0 (ABS_X), value 17758
Event: time 1334239142.663356, type 3 (EV_ABS), code 1 (ABS_Y), value 12440
Event: time 1334239142.663363, -------------- SYN_REPORT ------------
Event: time 1334239142.671316, type 3 (EV_ABS), code 0 (ABS_X), value 17754
Event: time 1334239142.671320, type 3 (EV_ABS), code 1 (ABS_Y), value 12065
Event: time 1334239142.671324, -------------- SYN_REPORT ------------
Event: time 1334239142.679320, type 3 (EV_ABS), code 0 (ABS_X), value 17746
Event: time 1334239142.679324, type 3 (EV_ABS), code 1 (ABS_Y), value 11727
Event: time 1334239142.679328, -------------- SYN_REPORT ------------
Event: time 1334239142.687364, type 3 (EV_ABS), code 0 (ABS_X), value 17732
Event: time 1334239142.687368, type 3 (EV_ABS), code 1 (ABS_Y), value 11432
Event: time 1334239142.687372, -------------- SYN_REPORT ------------
Event: time 1334239142.695348, type 3 (EV_ABS), code 0 (ABS_X), value 17699
Event: time 1334239142.695352, type 3 (EV_ABS), code 1 (ABS_Y), value 11153
Event: time 1334239142.695356, -------------- SYN_REPORT ------------
Event: time 1334239142.703332, type 3 (EV_ABS), code 0 (ABS_X), value 17615
Event: time 1334239142.703335, type 3 (EV_ABS), code 1 (ABS_Y), value 10902
Event: time 1334239142.703340, -------------- SYN_REPORT ------------
Event: time 1334239142.711373, type 3 (EV_ABS), code 0 (ABS_X), value 17560
Event: time 1334239142.711377, type 3 (EV_ABS), code 1 (ABS_Y), value 10695
Event: time 1334239142.711382, -------------- SYN_REPORT ------------
Above, you'll notice a couple of lines do not report an ABS_X value, so perhaps the driver is interpreting that to mean ABS_X has a value of zero, rather than no change?
Also, this tablet is a UC-LOGIC WP8060U as mentioned above, sold under the Monoprice brand, in particular this one: https://www.monoprice.com/products/product.asp?c_id=108&cp_id=10841&cs_id=1084101&p_id=5553&seq=1&format=2
|
|
From: Favux ... <fav...@gm...> - 2012-04-11 19:44:24
|
Hi,
Perhaps a Pressure Threshold is the most important missing feature.
That allows users who's tablet is too sensitive or insensitive to
their stylus, or their method of using the stylus, to change the
Threshold setting. With the WizardPen driver you could set a "cut
off" on the z-axis. Say "50, 1023". If I recall correctly some have
needed a "cut off" as high as 150. Evdev tablet would benefit from
having a similar feature.
>From 'man wacom':
Option "Threshold" "number"
sets the pressure threshold used to generate a button 1
events of stylus. The threshold applies to the normalised
pressure range of [0..2048]. The default is 27.
>From 'man xsetwacom':
Threshold level
Set the minimum pressure necessary to generate a Button event
for the stylus tip, eraser, or touch. The pressure levels of
all tablets are normalized to 2048 levels irregardless of the
actual hardware supported levels. This parameter is independent
of the PressureCurve parameter. Default: 27, range of 0 to
2047.
The Wacom X driver treats Threshold and PressureCurve independently.
There was talk of linking them but I think it was Peter who decided to
leave them independent.
Favux
|
|
From: Nikolai K. <sp...@gm...> - 2012-04-11 19:21:05
|
Hi Dima, On Mon, Apr 9, 2012 at 11:47 PM, Dima Ursu <dim...@gm...> wrote: > I will try that. I will search first for some documentation about > xf86-input-evdev... > btw... can you give me a link, or write here which are those tablet-related > features? The most dearly missed feature is, probably, pressure curve support [1]. Then, maybe, relative mode [2]. However, these are my personal guesses and it would be better to do a research - do a few Google searches, try asking people, take a look at which features wizardpen driver had recently. [1] See linuxwacom description at https://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Xsetwacom#PressureCurve [2] See linuxwacom description at https://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Xsetwacom#Mode Sincerely, Nick |
170 messages has been excluded from this view by a project administrator.
