https://bugs.kde.org/show_bug.cgi?id=386008
Alvin Wong <alvinhoc...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |critical
Summary|Shortcuts not working with |WinTab interfered by
|Wacom Feel drivers |synthesized touch events on
| |Windows ver 1709 (Fall
| |Creators Update)
Status|REOPENED |ASSIGNED
Assignee|krita-bugs-n...@kde.org |alvinhoc...@gmail.com
--- Comment #5 from Alvin Wong <alvinhoc...@gmail.com> ---
So, I suspect that MS decided \it is a good idea to synthesize touch events
from pen input...
It goes like this:
1. Pen event is sent through WinTab and Windows Ink by the driver
2. Krita takes the pen event from WinTab
3. Windows sends pen pointer events to Krita (since no lower level Windows Ink
APIs are in use), which are ignored
4. Something (I'd guess DefWindowProc) then synthesizes touch events, and then
mouse events
5. This probably upsets KisInputManager in some way?
I'll try to do a bit more digging...
--
You are receiving this mail because:
You are watching all bug changes.
