You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Enabling persistence will cause the window's "inner_pos" to be stored. When this position is read on the next launch, it appears to be applied to the window's outer position, resulting in the window being moved down 37 pixels each launch.
To Reproduce
Steps to reproduce the behavior:
Enable persistence feature
Launch app
Note window's position
Close and launch app again
Note window's position
Expected behavior
Window is initialized in the same place each launch.
Desktop (please complete the following information):
OS: Fedora 36 (Gnome)
The text was updated successfully, but these errors were encountered:
macOS: The top left corner position of the window content, the window’s “inner” position. The window title bar will be placed above it. The window will be positioned such that it fits on screen, maintaining set inner_size if any. If you need to precisely position the top left corner of the whole window you have to use Window::set_outer_position after creating the window.
Windows: The top left corner position of the window title bar, the window’s “outer” position. There may be a small gap between this position and the window due to the specifics of the Window Manager.
X11: The top left corner of the window, the window’s “outer” position.
So the only platform that uses inner_pos to set the window position is MacOS, other platforms use the outer window position.
Describe the bug
Enabling persistence will cause the window's "inner_pos" to be stored. When this position is read on the next launch, it appears to be applied to the window's outer position, resulting in the window being moved down 37 pixels each launch.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Window is initialized in the same place each launch.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: