| Summary: | When a PyQt5 application uses move() to set the position of the main window KDE offsets the window position | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Barry Scott <barry> |
| Component: | core | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | bshah, plasma-bugs-null, rdieter |
| Priority: | NOR | ||
| Version First Reported In: | 5.5.5 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Barry Scott
2016-03-13 11:59:49 UTC
"Depends" - you can expect "x,y" to be the final position of *your* window, not the framed window. However, I've no idea what PyQt is doing behind the scenes, can you attach a simple testcase (to inspect what's going on)? kwin is doing the right thing if I use the right Qt API. For record the right thing to do is use saveGeometry()/restoreGeometry() to have an applications window restored to the position and size the user left it in. The wrong thing to do is use moveEvent() to find position and resizeEvent() to find the size to save. Then use resize() and move() to restrore them. Qt does some "magic" under the covers to have restoreGeometry() do the right thing. Apologies for the false bug report. |