Bug 406191 - Tools stop working after passing over panels.
Summary: Tools stop working after passing over panels.
Status: RESOLVED UPSTREAM
Alias: None
Product: krita
Classification: Applications
Component: Tools (show other bugs)
Version: git master (please specify the git hash!)
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-03 16:57 UTC by lygamingac
Modified: 2019-04-03 18:14 UTC (History)
2 users (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 lygamingac 2019-04-03 16:57:50 UTC
SUMMARY:
Every tool stops working after going out of the canvas.

It ONLY happens when you use pen-table. The bug is not present in mouse. Even pen-table in mouse mode triggers the same problem


STEPS TO REPRODUCE
1. Make sure that "cursor shape" in option is set to "No cursor"  for a better observation.
2. In the canvas, and without the cursor, the tools should be working as usual.
3. Move the cursor to  any panels (out of the canvas) and then back to the working space.

OBSERVED RESULT
1. The cursor will stuck with it's last state in the panels (resizing, arrow, etc.)
2. Tools would stop working.
3. Change to another windows and then back to Krita has 2 results:
 - If the cursor was in the panel when Krita becomes the active window again --> The tools won't be stop working again, unless you change the windows again. But the cursor will ALWAYS be present: it won't hide.
 - If the cursor was in the canvas when Krita becomes the active window again --> The state resets and the bug can be triggered again



EXPECTED RESULT
The cursor should not display when it's set to no-display.
The tools should be working at any time




SOFTWARE/OS VERSIONS
Linux/Archlinux
Kernel: x86_64 Linux 5.0.5-arch1-1-ARCH



ADDITIONAL INFORMATION
Wacom-tablet with lib-wacom driver
Krita version: 4.1.8
video: https://drive.google.com/file/d/15azUsiFRMXABCyclfrJfqOAsmST1A6um/view?usp=sharing
Comment 1 Halla Rempt 2019-04-03 16:59:55 UTC
This is caused by bugs in Qt 5.12. Our appimages have patches to Qt that fix that; you can ask the Arch maintainers to use those patches until Qt integrates them. They have been submitted upstream. We cannot fix that in Krita.

If you want to actually use Krita, use the stable appimages. In the daily appimage builds, Python scripting is currently broken, also because of Qt 5.12.
Comment 2 Antonio Rojas 2019-04-03 17:40:12 UTC
Which of the patches in https://cgit.kde.org/krita.git/tree/3rdparty/ext_qt are relevant for this issue?
Comment 3 Halla Rempt 2019-04-03 18:14:17 UTC
These are all important when builing Krita against Qt 5.12:

0010-Fix-tablet-jitter-on-X11.patch
0011-Add-an-ID-for-recognition-of-UGEE-tablets.patch
0012-Synthesize-Enter-LeaveEvent-for-accepted-QTabletEven.patch
0013-Poison-Qt-s-headers-with-a-mark-about-presence-of-En.patch