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

Joshua Goins <j...@redstrate.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |NOT A BUG
             Status|CONFIRMED                   |RESOLVED

--- Comment #2 from Joshua Goins <j...@redstrate.com> ---
(In reply to Nicolas Fella from comment #1)
> The default button functionality is entirely application-defined, so there's
> nothing we can really show here

Correct, so I'm closing this. To add onto the confusion, this is under the
assumption the pen buttons are doing what they're supposed to be doing
correctly, and that said information is relayed to libwacom/libinput. I took a
look at the bug report, and their pen side buttons are sending... pen contact
and pen eraser contact events(???) which isn't great. Ideally their kernel
driver sends well-defined button events, and the hardware would have a
definition in libwacom - so everyone up and down the stack knows how to
translate them properly into something usable.

In the correct scenario, all pen buttons are application-defined (this is also
our default) and currently there's no way for Plasma/KWin/anyone to know what
the application does with them. So it's unactionable for us until that's
resolved somehow.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to