Bug 381067 - Keyboard shortcuts not working
Summary: Keyboard shortcuts not working
Status: RESOLVED DUPLICATE of bug 383911
Alias: None
Product: krita
Classification: Applications
Component: Shortcuts and Canvas Input Settings (show other bugs)
Version: 3.1.4
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-10 15:07 UTC by Niall
Modified: 2018-02-06 09:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Niall 2017-06-10 15:07:43 UTC
Hi,

Got an issue with the following application involving the pan function. It does not seem to work in certain circumstances.

Application - Krita 3.1.4 
System - Mac OS X (El Capitan Ver.10.11.6)

Bug Reproduction
-----------------

I've got the keyboard shortcut scheme set to emulate Photoshop via the preferences. So in this instance, the pan function is set to the space bar.

I have the brush tool selected. 

If I zoom (Cmd + '+/-') in or out of the canvas, then click on the canvas, the pan function works correctly. 

If I zoom in or out, then immediately press space bar to pan, it doesn't work, regardless if I have the mouse cursor over the canvas or not. 

This also applies to the colour spot tool, pressing (Cmd) whilst brush tool is selected.

In some circumstances however, clicking on the canvas does not resolve bug, I either need to click on the UI (Layer, brush, colour palette, etc.) Or pressing (Ctrl +Tab).

It's a small bug, but one that impedes my workflow quite considerably! X_X;;

Hope this info helps. If you require any further info from me, give me a shout.

Cheers.

Niall
Comment 1 Halla Rempt 2017-06-10 15:54:17 UTC
Hi Niall,

I think I've heard other reports like this, but I cannot find them right now. It seems it's actually a bug in the development framework, but I'm not sure either...
Comment 2 Halla Rempt 2018-02-06 09:47:04 UTC

*** This bug has been marked as a duplicate of bug 383911 ***