Summary: | Okular does not remember window position | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Adiost <me> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | minor | CC: | aacid, nate |
Priority: | NOR | ||
Version: | 1.8.1 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Microsoft Windows | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=409675 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Adiost
2019-10-12 17:50:36 UTC
Yep, this is up to the application to store and remember (on both Windows and Linux). Completely disagree, it's none of the applications responsibility to position itself. Let the window manager do it's job. Moreover in any sane modern windowing system you can't know where you are, so you can't restore yourself either. KWin developers say it's the application's job to request placement. IMHO the toolkit should bridge both expectations, and from what I know, KMainWindow used to help there. Not sure what the replacement for Qt5 was. (In reply to Albert Astals Cid from comment #2) > Completely disagree, it's none of the applications responsibility to > position itself. Let the window manager do it's job. > > Moreover in any sane modern windowing system you can't know where you are, > so you can't restore yourself either. That's exactly that I would have said too, except for KWin's developers feel pretty strongly that it's not the window manager's job to remember window positions. See Bug 15329. Found out that KXMLGui is supposed to be doing this. *** This bug has been marked as a duplicate of bug 415150 *** |