Bug 482166

Summary:	problem with space key
Product:	[Applications] krita	Reporter:	trolinotrolowaty
Component:	Tools/Move	Assignee:	Krita Bugs <krita-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	dimula73
Priority:	NOR
Version First Reported In:	5.1.5
Target Milestone:	---
Platform:	Compiled Sources
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description trolinotrolowaty 2024-03-01 15:36:59 UTC

I have a problem with space key 
Sometimes, but only sometimes, when i double/triple tap (click few times in general) (I'm using defoult keys; "=", "-") too zoom out/zoom in, my space key (to move around the canvas) isnt working
No metter where i click it, nor keyboard nor tablet's pen are responding 
I've tried to check if it can be problem with my software or my graphic tablet, so I've tried to check if any key is hold, but nothing like this is happening
It must be Krita problem
I have an idea (since this problem wasn't present from beggining with your program) that I can just using too many layers now and Krita just bugs out from too many information, but I have no idea if its possible 
It's so frustrating and restarting Krita doesn't help 
Please help

Comment 1 Dmitry Kazakov 2024-03-01 15:39:50 UTC

Hi, trolinotrolowaty!

Could you please try an updated version of Krita 5.2.2? I remember I fixed some issues in this area since 5.1.5

Comment 2 trolinotrolowaty 2024-03-01 16:26:27 UTC

(In reply to Dmitry Kazakov from comment #1)
> Hi, trolinotrolowaty!
> 
> Could you please try an updated version of Krita 5.2.2? I remember I fixed
> some issues in this area since 5.1.5

I've apdated my Krita and nothing changed
Also i played with settings and no metter witch key i bind with this function its just isn't working
I've tried on brand new, blank file and my issue isn't pressent, but increasing assigned performance for Krita doesn't solve the problem
since I've updated the version - is home page customizable? Im not fun of this new look

Comment 3 Bug Janitor Service 2024-03-02 03:47:01 UTC

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.