[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:       2018-03-30 11:35:50
Message-ID: bug-371827-17878-XvcKteVAts () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=371827

--- Comment #13 from Aidan Walton <aidan.walton@gmail.com> ---
Hey, this is such a shame. I remember Krita working just fine some time back.
So whatever changed has still not been resolved. Or quite simply I am missing
something obvious. I have said this before and I wish to help, but it seems we
are coming at this from the wrong angle.
I have limited options from a driver point of view. The evdev system in Linux
is well defined. OK, exactly how the 'Abs Misc' Valuator Class is handled is a
corner case.

But.... It seems very clear. XIValuatorClass: Label: Abs Pressure. Is very
obviously used for one purpose and one purpose only. Pen pressure reporting.

My driver does exactly this, and these other applications seem very satisfied
to use it appropriately. 

BTW as a side note, when I try to enable tablet event logging "SHIRT+CTRL+T" I
get no output to the console.???? So its quite impossible to even attempt to
debug this from an application level. I cant find any documentation to help any
further.

So from what I understand this is how the Linux device stack looks:

X11:
Linux kernel → libevdev → xf86-input-evdev → X server → X client

Wayland:
Linux kernel → libevdev → libinput → Weston → Wayland client

If I examine xinput (X11) or libinput (Wayland) both report pressure to the
client.

What one earth is Krita doing with this well defined information?

I'm done!

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]