[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 --- Comment #42 from Nate Graham --- Using it directly from C++ is fine, and some QtWidgets apps like Konsole already do that because they want finer-grained control over the behavior compared to what KMainWindow offers by default. I think it would be

[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 --- Comment #41 from David Redondo --- https://invent.kde.org/frameworks/kconfig/-/blob/master/src/gui/kwindowconfig.h is a thing which is used by KMainWindow already, either we need a convenient QML type to wrap this or use it directly. -- You are re

[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 --- Comment #40 from Nate Graham --- Apps using Kxmlgui::MainWindow get this automatically. For QML apps which don't use Kxmlgui, we definitely need something standardized, yeah. -- You are receiving this mail because: You are watching all bug changes

[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 --- Comment #39 from Plata --- If I understood correctly, every app is supposed to include the same boilerplate code. So: is there at least a template somewhere for developers to understand how the whole window state handling/restoration should be done

[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=434116|

[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=450053|

[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=392375|

[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=392375|

[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b |

[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 --- Comment #38 from Nate Graham --- Also this is not truly fully fixed. System Monitor remembers that it was maximized, but it also inappropriately saves its new maximized geometry on quit, so when you unmaximize it, it fails to restore to the size it

[kwin] [Bug 437089] On Wayland, System Monitor does not remember maximized state when closed while maximized and later re-opened

https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added Summary|On Wayland, Windows that|On Wayland, System Monitor |wer