Bug 409377 - Kolourpaint main window out of focus after resizing image.
Summary: Kolourpaint main window out of focus after resizing image.
Status: RESOLVED DUPLICATE of bug 405991
Alias: None
Product: kolourpaint
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: kolourpaint-support
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-01 16:09 UTC by Mikael
Modified: 2019-07-01 16:13 UTC (History)
0 users

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


Attachments
Before resizising global menu is working and window is in focus (52.86 KB, image/png)
2019-07-01 16:09 UTC, Mikael
Details
After resize global menu doesn't work and window is out of focus (48.48 KB, image/png)
2019-07-01 16:10 UTC, Mikael
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikael 2019-07-01 16:09:32 UTC
Created attachment 121265 [details]
Before resizising global menu is working and window is in focus

SUMMARY
After resizing the image/drawable area the main window of the program gets out of focus and clicking it doesn't bring it back. Only minimizing or activating other window and then clicking Kolourpaint window brings back the focus.

STEPS TO REPRODUCE
1. Resize image with handles
2. Main window out focus (Globalmenu doesn't show up)
3. Minimize kolourpaint window or click outside off the window
4. Main window now has the focus again

OBSERVED RESULT
Global menu gets disabled after resizing image.

EXPECTED RESULT
Resizing image shouldn't interfere with the window focus

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 4.19.49-1-MANJARO
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
See attachments for demonstration
Comment 1 Mikael 2019-07-01 16:10:10 UTC
Created attachment 121266 [details]
After resize global menu doesn't work and window is out of focus
Comment 2 Mikael 2019-07-01 16:13:03 UTC
*** This bug has been marked as a duplicate of bug 405991 ***