SUMMARY Pan tool does not work via its default shortcuts (Space + leftclick, and middleclick). STEPS TO REPRODUCE 1. Open Krita 2. Open big document 3. Try to navigate. OBSERVED RESULT The mouse cursor does not change from the currently-selected tool EXPECTED RESULT Mouse cursor changes, and can pan. SOFTWARE/OS VERSIONS Windows: 11 Stable ADDITIONAL INFORMATION Installed via Microsoft Windows Store
Hi! Can you check if the Canvas Input Profile (Settings -> Configure Krita) has these shortcut assigned to Pan Canvas action (check if you are using Krita Default profile/or something else that you made yourself). If it is assigned, and it still doesn't work, can you please share the file in C:\Users\<username>\AppData\Roaming\krita\input corresponding to the profile name that is active.
Created attachment 159813 [details] attachment-1156811-0.html 1. I didn't change anything. 2. It is in fact set to those things. 3. There are more bugs than just this with the shortcuts. Zoom doesn't work either. Using the Zoom tool itself is also bugged: it only zooms in, never out. I have to set the Zoom factor in the bottom right control in the window. Ryan Johnson | 🔗My Profile<https://linkr.bio/AMDphreak> | GSO<https://www.germantownsymphony.org> member, FSF, EFF supporter ________________________________ From: sh_zam <bugzilla_noreply@kde.org> Sent: Wednesday, June 21, 2023 8:45 AM To: rj.amdphreak@gmail.com <rj.amdphreak@gmail.com> Subject: [krita] [Bug 471294] Pan tool shortcuts not working https://bugs.kde.org/show_bug.cgi?id=471294 sh_zam <shzam@sdf.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |triaged CC| |shzam@sdf.org Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #1 from sh_zam <shzam@sdf.org> --- Hi! Can you check if the Canvas Input Profile (Settings -> Configure Krita) has these shortcut assigned to Pan Canvas action (check if you are using Krita Default profile/or something else that you made yourself). If it is assigned, and it still doesn't work, can you please share the file in C:\Users\<username>\AppData\Roaming\krita\input corresponding to the profile name that is active. -- You are receiving this mail because: You reported the bug.
*** Bug 471295 has been marked as a duplicate of this bug. ***
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, Ryan! Could you please make a video recording of the problem? I cannot reproduce it here. It would also be helpful if you could try the nightly build of Krita from here: https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/lastSuccessfulBuild/artifact/krita-nightly-x64-5.2.0-prealpha-6d578e3bbb.zip
Created attachment 159873 [details] attachment-1349348-0.html A video recording of a keyboard shortcut not working? I can give you logs if you tell me what to give you. You can't just trust that I know when my finger is typing? I have a WPM of over 100, and a computer science degree, and have been using programs since 1997. I think I know when a keyboard shortcut isn't working. Especially when other keyboard shortcuts are working in the same program. I had a problem with another software like this, due to AMD Software Adrenalin Edition capturing the key combinations, however those shortcuts have been disabled in AMD Software, and the other application now responds appropriately. I don't have any other applications that capture keyboard input running in the background. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Jun 22, 2023 at 9:47 AM Dmitry Kazakov <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=471294 > > Dmitry Kazakov <dimula73@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |dimula73@gmail.com > Status|REPORTED |NEEDSINFO > > --- Comment #5 from Dmitry Kazakov <dimula73@gmail.com> --- > Hi, Ryan! > > Could you please make a video recording of the problem? I cannot reproduce > it > here. > > It would also be helpful if you could try the nightly build of Krita from > here: > > https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/lastSuccessfulBuild/artifact/krita-nightly-x64-5.2.0-prealpha-6d578e3bbb.zip > > -- > You are receiving this mail because: > You reported the bug.
> You can't just trust that I know when my finger is typing? It is less to do with trust and more to do with us seeing if there is any change in the UI of Krita to give us a clue about what might be going wrong with the bug. Especially since you suggest that all the configs were left untouched.
Hi, Ryan! By "recording" I meant not "recording of your fingers", but recording of your screen (via, e.g., OBS Studio) :) You can actually also summon the on-screen-keyboard so we could see what keys are pressed at the moment. That is needed so we could see how Krita reacts to your shortcuts and what actually happens. It might also be a good idea to reset your Krita configurations. Try to move these files/folders into some safe space: %LOCALAPPDATA%\kritarc %APPDATA%\krita\input There used to be some bugs that could cause clashes with shortcuts during some of updates of Krita
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Dmitry Kazakov from comment #9) > Hi, Ryan! > > By "recording" I meant not "recording of your fingers", but recording of > your screen (via, e.g., OBS Studio) :) You can actually also summon the > on-screen-keyboard so we could see what keys are pressed at the moment. That > is needed so we could see how Krita reacts to your shortcuts and what > actually happens. > > It might also be a good idea to reset your Krita configurations. Try to move > these files/folders into some safe space: > > %LOCALAPPDATA%\kritarc > %APPDATA%\krita\input > > There used to be some bugs that could cause clashes with shortcuts during > some of updates of Krita No offense, but how is a screen recording supposed to show anything when the keyboard shortcuts do not work and are not visible? You're just going to be staring at a fixed frame the entire video and/or listening to me gripe.
(In reply to Dmitry Kazakov from comment #9) > Hi, Ryan! > > By "recording" I meant not "recording of your fingers", but recording of > your screen (via, e.g., OBS Studio) :) You can actually also summon the > on-screen-keyboard so we could see what keys are pressed at the moment. That > is needed so we could see how Krita reacts to your shortcuts and what > actually happens. > > It might also be a good idea to reset your Krita configurations. Try to move > these files/folders into some safe space: > > %LOCALAPPDATA%\kritarc > %APPDATA%\krita\input > > There used to be some bugs that could cause clashes with shortcuts during > some of updates of Krita It was a fresh install of Krita from Microsoft App Store. Yeah, I paid for the store version bc I like the software.
This bug still needs info from the reporter.
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!