Summary: | Konsole remembers window size across launches, but not position | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Nate Graham <nate> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kishore96, nate |
Priority: | NOR | ||
Version: | 17.04.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nate Graham
2017-06-04 03:10:09 UTC
> the new window always spawns at 0,0.
Even if your KWin settings default to "center"?
The obvious workaround is to use KWin rules to force an initial position.
Revert accidental status change. If I choose "Centered", then the window spawns in the center of the screen. But that's not what I want. I want it to spawn in the same location that it was in the last time I closed it. Size is already correctly remembered across launches in this manner, but location isn't. I am aware of workarounds such as KWin positioning rules. Workarounds are great, but even greater is fixing the bug that requires the workaround! :) (In reply to Nate Graham from comment #3) > If I choose "Centered", then the window spawns in the center of the screen. > But that's not what I want. I want it to spawn in the same location that it > was in the last time I closed it. Size is already correctly remembered > across launches in this manner, but location isn't. > > I am aware of workarounds such as KWin positioning rules. Workarounds are > great, but even greater is fixing the bug that requires the workaround! :) There is an option called placement option called 'smart', which if I understand correctly, will do what you want. "Smart" is the default setting, and the one I'm using. If Smart is supposed to remember window position, then the bug here is that it's not--at least for Konsole. Not limited to Konsole; this is a limitation of KWin itself, which controls window placement. Marking as a duplicate of https://bugs.kde.org/show_bug.cgi?id=384091 *** This bug has been marked as a duplicate of bug 384091 *** |