Bug 443694 - If pop-up palette is closed when the cursor is outside the palette, canvas cursor doesn't switch to system cursor when hovering into dockers
Summary: If pop-up palette is closed when the cursor is outside the palette, canvas cu...
Status: RESOLVED DUPLICATE of bug 441370
Alias: None
Product: krita
Classification: Applications
Component: General (other bugs)
Version First Reported In: 5.0.0-beta2
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: Dmitry Kazakov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-14 06:50 UTC by tomtomtomreportingin
Modified: 2021-10-14 07:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tomtomtomreportingin 2021-10-14 06:50:42 UTC
SUMMARY
If the user closes the pop-up palette with a stylus while the cursor is outside the pop-up palette, the cursor will not properly switch to the system cursor when hovering into the docker area. This behavior stops when something in the docker area is clicked or the cursor travels outside the Krita window. 

This behavior is most noticeable when Cursor Shape is set to "No Cursor", as the cursor essentially becomes invisible in that case.

Observed in beta 1, beta 2, and 5.1.0-prealpha git 6a41c43. Does not occur in Krita 4, so it is a regression. Happens regardless if it's the triangle selector or wide gamut selector.

STEPS TO REPRODUCE
1. Open the pop-up palette.
2. Right-click or left-click outside the pop-up palette with a stylus.
3. Hover into the docker area.

OBSERVED RESULT
The cursor doesn't switch to the system cursor.

EXPECTED RESULT
The cursor switches to the system cursor.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.12.11 (Appimage)
Comment 1 Wojtek Trybus 2021-10-14 07:27:49 UTC
I mark it as a duplicate of a bug I reported for beta1.

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