Skip to content
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

Closed
ThomasAdam opened this issue May 9, 2020 · 0 comments · Fixed by #69
Closed

Unmaximizing windows can sometimes vanish #68

ThomasAdam opened this issue May 9, 2020 · 0 comments · Fixed by #69
Assignees
Labels
type:bug Something's broken!
Projects
Milestone

Comments

@ThomasAdam
Copy link
Member

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.

@ThomasAdam ThomasAdam added the type:bug Something's broken! label May 9, 2020
@ThomasAdam ThomasAdam added this to the 1.0 milestone May 9, 2020
@ThomasAdam ThomasAdam self-assigned this May 9, 2020
@ThomasAdam ThomasAdam added this to To do in FVWM3 via automation May 9, 2020
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
FVWM3 automation moved this from To do to Done May 9, 2020
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
Labels
type:bug Something's broken!
Projects
Status: Done
FVWM3
  
Done
Development

Successfully merging a pull request may close this issue.

1 participant