Bug 428107

Summary:	Adding new layer for the first time moves UI focus to blending mode menu
Product:	[Applications] krita	Reporter:	rudeb0y
Component:	Layer Stack	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	minor	CC:	ahab.greybeard, aiena.makehuman, halla
Priority:	NOR
Version First Reported In:	4.4.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description rudeb0y 2020-10-22 16:11:15 UTC

SUMMARY
Adding a new layer for the first time in a new document moves the UI focus to the blending mode menu. You need to select another layer in the layer panels menu to unfocus the blending menu if you want to use the the panning or zoom tool. drawing on the canvas doesn't seem to unfocus the menu. Subsequent newly created layers don't "steal" focus from the canvas, it's only the first new layer.

Drawing, panning, zooming first, then creating a new layer display the same behavior: blending mode is focused
I managed to unfocus the menu after layer creation in other ways (drawing and drawing again a couple of times; switching focus to another workspace and back; clicking around in the UI), but none seem to work consistently other than selecting another layer.

STEPS TO REPRODUCE
1. Open Krita, create new document by clicking on the link on the welcome screen
2. add a new layer by clicking on the "+" at the bottom of the new layer panel
3. hold space to pan on the canvas

OBSERVED RESULT

the blending mode menu drops down

EXPECTED RESULT

cursor changes into hand and canvas can be panned

WORKAROUND

select another layer, then the newly created layer again.

SOFTWARE/OS VERSIONS
Arch Linux, current as of 2020-10-22 17:48
no DE, WM: sway 1.5-1 
Qt Version: qt5-base 5.15.1-3

ADDITIONAL INFORMATION
2 screens, layers menu is on second screen.
control scheme set to Photoshop-like.
pan = hold space
zoom = hold ctrl+space

Comment 1 Halla Rempt 2020-10-22 16:13:46 UTC

Hm, no, I cannot reproduce this. Please try to reproduce it with the appimage, instead of the distribution build of Krita, since that has a lot of patches to Qt. And check whether using another window manager makes a difference, too.

Comment 2 aiena.makehuman 2020-10-22 16:35:36 UTC

I cannot reproduce this either. I am on kubuntu though.

Comment 3 rudeb0y 2020-10-22 18:34:19 UTC

Same thing with appimage. Also tested with the layers panel on the same screen without success. I'll see what I can do about another WM.

Comment 4 rudeb0y 2020-10-22 19:08:23 UTC

I can reproduce it with plasma desktop started with wayland.

Comment 5 Bug Janitor Service 2020-10-23 04:33:18 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.

Comment 6 Ahab Greybeard 2020-10-23 08:13:29 UTC

I can reproduce this on Debian 10 with the 4.2.9 appimages onwards and also on Windows 10 with the 4.4.0 installed version and a recent 5.0.0 prealpha portable .zip package.

It only happens if the Layers docker is floating. It happens with a new file or a freshly opened file in a new session.

If you add a new paint layer to the top of the layer stack, having done nothing else, it happens repeatedly (when Space is pressed) with each new paint layer even if you paint on the canvas after pressing Space.

If you add a new layer and then click anywhere in the main window, it does not happen again until you add another new layer at the top of the layer stack.

At this stage it also happens with any additional new images that are created.

If you select any other layer at any time and then go back to the top of the layer stack, it does not happen again with that image or with an additional new image in the same session.

If you then close all open images, the behaviour returns when you create/open a new image.

Comment 7 Halla Rempt 2020-10-23 08:41:43 UTC

Ah, that's the essential point: the docker is floating. I am sure we have a duplicate for this issue, but I'm also pretty sure we can't really do anything about the focus issues in this case.

Comment 8 rudeb0y 2020-10-23 16:22:11 UTC

can confirm that the docker is floating in my case too.

Comment 9 Halla Rempt 2022-09-19 13:13:52 UTC

Closing this since there's nothing we can do about the focus handling of floating dock widgets.