https://bugs.kde.org/show_bug.cgi?id=451424
Halla Rempt <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Halla Rempt <[email protected]> --- I can confirm the issue, though I doubt it's related to deif_lou's work. This is more likely, since it's not in 5.0.2 (but it is in the krita/5.0 branch): commit 58392a1f9ae446da3f48c632f2bfe68d10a60ee4 Au58392a1f9ae446da3f48c632f2bfe68d10a60ee4thor: Dmitry Kazakov <[email protected]> Date: Sat Jan 8 17:18:02 2022 +0300 Fix Krita forgetting about pressed keys when tapping Ctrl too quickly Under some circumstances, KeyPress/KeyRelease event comes **after** a tablet move event with already updated state. It is not very clear how that happens, but it is surely not impossible. Qt fills modifiers event property by reading some global storage, so it is possible that this state is not entirely in sync with the events queue. The patch does two fixes: 1) KisShortcutMatcher::recoveryModifiersWithoutFocus() used RecursionNotifier incorrectly, causing keyReleased() and keyPressed() to reset the state. -- You are receiving this mail because: You are watching all bug changes.
