[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [krita] [Bug 371827] [BOSTO] Pen Pressure not working
From: Aidan Walton <bugzilla_noreply () kde ! org>
Date: 2016-10-31 21:58:22
Message-ID: bug-371827-17878-UDEz0zy4tl () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=371827
--- Comment #5 from Aidan Walton <aidan.walton@gmail.com> ---
(In reply to Boudewijn Rempt from comment #3)
> Do you get any message like
>
> "QApplication: Failed to get list of tablet devices"
>
> ?
Well, this is not so easy to fathom.
If it helps and you have a chance, please take a look.
# xinput --list --long 11
Bosto Kingtee 22HD id=11 [slave pointer (2)]
Reporting 5 classes:
Class originated from: 11. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Unknown" "Button Unknown" "Button
Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left"
"Button Horiz Wheel Right"
Button state:
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 0:
Label: Abs X
Range: 0.000000 - 10206.000000
Resolution: 0 units/m
Mode: absolute
Current value: 7502.000000
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 1:
Label: Abs Y
Range: 0.000000 - 7422.000000
Resolution: 0 units/m
Mode: absolute
Current value: 5450.000000
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 2:
Label: Abs Pressure
Range: 0.000000 - 2048.000000
Resolution: 0 units/m
Mode: absolute
Current value: 0.000000
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 3:
Label: Abs Misc
Range: 0.000000 - 0.000000
Resolution: 0 units/m
Mode: absolute
Current value: 2.000000
We can see everthing needed including presure.
# tail -f /var/log/Xorg.0.log
[ 38062.162] (II) config/udev: Adding input device Bosto Kingtee 22HD
(/dev/input/mouse2)
[ 38062.162] (II) No input driver specified, ignoring this device.
[ 38062.162] (II) This device may have been added with another device file.
[ 38062.233] (II) config/udev: Adding input device Bosto Kingtee 22HD
(/dev/input/event5)
[ 38062.233] (**) Bosto Kingtee 22HD: Applying InputClass "evdev tablet
catchall"
[ 38062.233] (II) Using input driver 'evdev' for 'Bosto Kingtee 22HD'
[ 38062.233] (**) Bosto Kingtee 22HD: always reports core events
[ 38062.233] (**) evdev: Bosto Kingtee 22HD: Device: "/dev/input/event5"
[ 38062.233] (--) evdev: Bosto Kingtee 22HD: Vendor 0xb57 Product 0x9016
[ 38062.233] (--) evdev: Bosto Kingtee 22HD: Found absolute axes
[ 38062.233] (--) evdev: Bosto Kingtee 22HD: Found x and y absolute axes
[ 38062.233] (--) evdev: Bosto Kingtee 22HD: Found absolute tablet.
[ 38062.233] (II) evdev: Bosto Kingtee 22HD: Configuring as tablet
[ 38062.233] (**) evdev: Bosto Kingtee 22HD: YAxisMapping: buttons 4 and 5
[ 38062.233] (**) evdev: Bosto Kingtee 22HD: EmulateWheelButton: 4,
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 38062.233] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:0b.0/usb2/2-6/2-6:1.0/input/input76/event5"
[ 38062.233] (II) XINPUT: Adding extended input device "Bosto Kingtee 22HD"
(type: TABLET, id 11)
[ 38062.233] (II) evdev: Bosto Kingtee 22HD: initialized for absolute axes.
[ 38062.233] (**) Bosto Kingtee 22HD: (accel) keeping acceleration scheme 1
[ 38062.233] (**) Bosto Kingtee 22HD: (accel) acceleration profile 0
[ 38062.233] (**) Bosto Kingtee 22HD: (accel) acceleration factor: 2.000
[ 38062.233] (**) Bosto Kingtee 22HD: (accel) acceleration threshold: 4
Well its mapped by evdev for sure, but no mention of pressure? yet xinput shows
it. Alos udev maps the device as a generic mouse, as indeed it should. So the
question is for you is Qt recognising these Valuators.
I refer to this old bug: https://bugreports.qt.io/browse/QTBUG-48370
Description
It's not detected as a tablet, so only works as a mouse.
[ 0.001 D] unknown - input device WALTOP International Corp. Slim Tablet
[ 0.001 D] unknown - has 13 buttons
[ 0.001 D] unknown - has valuator "Abs X" recognized? true
[ 0.001 D] unknown - has valuator "Abs Y" recognized? true
[ 0.001 D] unknown - has valuator "Abs Pressure" recognized? true
[ 0.001 D] unknown - has valuator "Rel Vert Wheel" recognized? true
[ 0.001 D] unknown - it's a scrolling device
So this was a Waltop tablet, as can be seen Qt seems to identify the needed
functions based on the Valuator Label: Abs Presssure.
And as you can see my xinput displays the exact same Valuator Label from my
Bosto.
I think there is nothing much more I can change in the driver. Any thoughts.
And while I may have your attention, the final Valutor Label: Abs Misc, I am
using to define the current tool. Either Pen or Eraser.
I send '2' for PEN and '10' for ERASER. I have no idea if you even take any
notice of this, but I could send other EV_ codes instead, or any value you
would like to see in this 'Abs Misc' Valuator.
This does seem to be the current Linux generic method for mapping a Tablet into
X, so I don't want to start hacking xconfigs if this can work out of the box.
Help if you can.
Thanks
--
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic