Summary: | Krita's canvas shortcuts system picks up spurious inputs from completely unrelated windows and treats them as held down modifier keys | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Jo Valentine-Cooper <jvc> |
Component: | Shortcuts and Canvas Input Settings | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | cavendish.qi, dimula73, halla, miranda |
Priority: | NOR | ||
Version: | 5.1.3 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jo Valentine-Cooper
2022-12-08 05:38:28 UTC
Hi, Jo Valentine! Do you have any accessibility system running on your system? Or some custom input system support, like traditional Chinese? On every focus-in event Krita asks the system about the currently pressed keys and it seems OS reports 'e' key pressed for some reason. Does the problem happens with GVim only or with other applications as well? Setting to needsinfo (In reply to Dmitry Kazakov from comment #1) > Hi, Jo Valentine! > > Do you have any accessibility system running on your system? Or some custom > input system support, like traditional Chinese? On every focus-in event > Krita asks the system about the currently pressed keys and it seems OS > reports 'e' key pressed for some reason. > > Does the problem happens with GVim only or with other applications as well? Happens with other applications as well. I have no custom input systems running that I am aware of. I do have one program that modifies input - it's called W10Wheel.NET, and it enables simultaneous use of the middle mouse button as its own button and (when held down and the mouse is moved) as a "scroll wheel". I had ruled out that program out as a factor, however, because 1) it does not generate keyboard inputs, just mouse wheel, and 2) I have reproduced this bug when it is disabled and when it is not running at all. I should note also that it's not just the "e" key; that was one example. This morning just now, for example it was the keys 0 and t: "[ ] Enter " "[ ] FocusIn " "[ ] ShortcutOverride key: 0x30 mod: 0x0 text: none autorepeat: 0" "[ ] ShortcutOverride key: 0x54 mod: 0x0 text: none autorepeat: 0" "[ ] ShortcutOverride key: 0x30 mod: 0x0 text: 0 autorepeat: 0" Hope this helps! Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. Hi, Jo Valentine! Could you please test the latest nightly builds of Krita if this bug is still actual? We had multiple attempts to fix bugs like that since then https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ Haven't tried one of those builds, but I have version 5.2.1 here and am no longer experiencing the bug. At the very least I can't reproduce it anymore using the approach described earlier. Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. https://blogs.kde.org/2024/01/30/farewell-binary-factory-add-craft-jobs-your-apps-kdes-gitlab-now/ https://invent.kde.org/graphics/krita/-/jobs 1. How do you switch between Krita and other text editors? mouse click the app icon in task bar, or Win+Tab, etc? 2. Which Canvas Shortcuts don't work? give an example? Thanks. (In reply to Liang Qi from comment #9) > 1. How do you switch between Krita and other text editors? mouse click the > app icon in task bar, or Win+Tab, etc? > 2. Which Canvas Shortcuts don't work? give an example? > > Thanks. At the time, any means of switching windows seemed to trigger it, although I most commonly used either Alt-Tab, or the F10 key (which I have mapped to launch a new gvim window). And when it occurred, no shortcuts appeared to work - an example would be the 6 and 4 keys to rotate the canvas or use of the mousewheel to zoom in and out, as illustrated in the original report. That said, I haven't been able to reproduce this issue in over a year (yay!) so I'm having to go by distant memory... :) Hope this helps. |