Open yoonsangmin opened 5 months ago
I just found out that there is a latest version in the action. I confirmed that the issue of creating empty space is not present in the latest version. However, it still remembers the maximized state, and when reopened, it tiles in the maximized state.
It would be good if the application, when opened in a maximized state, does not tile, and stays maximized, or the application automatically unmaximizes when tiled.
can confirm I'm getting this behaviour too as of the latest commit
I recommend adding a window rule to KWin that sets the maximized state to false for new windows. KWin doesn't actually have a property for whether a window is maximized or not, so it's hard to tell if a window is maximized when added.
@zeroxoneafour Thank you. I think it will be great to add that window rule automatically by Polonium.
Should I close this issue?
Before you make the issue, confirm that
Describe the bug
Most KDE apps remember the maximized state. If you close the app while it's maximized, when you reopen it, it will tile in a maximized state. If you unmaximize it in that state, empty space appears in the tiled area. Even if you maximize it again, it stays tiled in the maximized state. The only solution is to either drag the window or use a shortcut to make it a floating window.
To reproduce
Close the window after maximizing it, and then reopen the application. Unmaximize the maximized window.
Expected behavior
A tiled window always opens in an unmaximized state, or if you cannot unmaximize it, a maximized window should avoid tiling.
Relevant log output
Screenshots and videos
https://github.com/zeroxoneafour/polonium/assets/26238363/0a323e84-dda6-4820-b890-130574cee450
Additional context
No response