-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unmaximizing windows can sometimes vanish #68
Comments
ThomasAdam
added a commit
that referenced
this issue
May 9, 2020
When moving a maximized window between pages or screens, FVWM records the previous geometry of the unmaximized window, so it can restore correctly. However, this doesn't work well when the maximized window itself has moved between screens or different pages, since the unmaximized geometry from the point of view of the maximized window is now incorrect. Subsequently, unmaximizing a window will put that window in to the ether. For now, the approach is to make unmaximizing a window imply MoveToScreen (relative to the window's screen) such that it remains visible, and should largely do what the user expects. Fixes #68
ThomasAdam
added a commit
that referenced
this issue
May 9, 2020
When moving a maximized window between pages or screens, FVWM records the previous geometry of the unmaximized window, so it can restore correctly. However, this doesn't work well when the maximized window itself has moved between screens or different pages, since the unmaximized geometry from the point of view of the maximized window is now incorrect. Subsequently, unmaximizing a window will put that window in to the ether. For now, the approach is to make unmaximizing a window imply MoveToScreen (relative to the window's screen) such that it remains visible, and should largely do what the user expects. Fixes #68
mikeandmore
pushed a commit
to mikeandmore/fvwm3
that referenced
this issue
Nov 28, 2020
When moving a maximized window between pages or screens, FVWM records the previous geometry of the unmaximized window, so it can restore correctly. However, this doesn't work well when the maximized window itself has moved between screens or different pages, since the unmaximized geometry from the point of view of the maximized window is now incorrect. Subsequently, unmaximizing a window will put that window in to the ether. For now, the approach is to make unmaximizing a window imply MoveToScreen (relative to the window's screen) such that it remains visible, and should largely do what the user expects. Fixes fvwmorg#68
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When moving a maximized window between pages or screens, FVWM records the previous geometry of the unmaximized window, so it can restore correctly.
However, this doesn't work well when the maximized window itself has moved between screens or different pages, since the unmaximized geometry from the point of view of the maximized window is now incorrect. Subsequently, unmaximizing a window will put that window in to the ether.
For now, the approach is to make unmaximizing a window imply
MoveToScreen
(relative to the window's screen) such that it remains visible, and should largely do what the user expects.The text was updated successfully, but these errors were encountered: