This prevents Krita from losing its Wintab button map, at the cost of
requiring Krita to be restarted (or else a new option to be added
allowing settings to be reset) when users change settings in the Wintab
driver.
BUG: 359561
BUG: 349422
Details
Details
- Reviewers
rempt - Group Reviewers
Krita - Maniphest Tasks
- T958: Fix tablet handling issues for Krita 3.0
- Commits
- R37:32ba9cbadb0f: Load Wintab button mapping only once.
Diff Detail
Diff Detail
- Repository
- R37 Krita
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
I think this is caused by a bug in the Wintab driver or at the very least a hideously ugly corner case. It seems wTInfo may return the wrong logical button map if Krita is not in focus but the tablet is used in Krita's window. The strange part is that wtInfo will then continue to send this bad button map even after you focus Krita and do another query after entering proximity.
(I also believe either the Wintab driver or Qt has a numerical error in the cursor mapping calculation. I'm quite certain the scaling in the Wintab code works correctly, but the cursor events generated by the driver and processed by Qt are consistently off by 3-5 pixels.)
Comment Actions
I'm fine with that limitation, and it would be really good to have those two bugs fixed!
Comment Actions
OK, if people start complaining it would probably be straightforward to add a menu option like "Reload tablet settings." But restarting Krita is practically as easy as that.