ianyh / Amethyst

Automatic tiling window manager for macOS à la xmonad.
https://ianyh.com/amethyst/
MIT License
14.8k stars 487 forks source link

Amethyst forgets about hidden or minimized windows on space change #1191

Open martin-braun opened 2 years ago

martin-braun commented 2 years ago

Describe the bug / To Reproduce Say you have 3 windows in the current space that are all aligned properly by Amethyst. When you now decide to hide an application (cmd + h) or minimize a window (cmd + m), other windows will re-align. If you bring the app back (i.e. by clicking on the app/window in the dock) Amethyst will re-align everything like it was initially. So far so good.

Now repeat the above, but change your current space and change the current space back before bringing the app back. You will see that Amethyst forgot about your previously-hidden app window when you switched the space, so a re-alignment won't be triggered. The only way to fix it is to trigger re-alignment manually or to simply change the space twice again.

Applications: Any

Expected behavior Re-align all windows when hidden or minimized applications/windows come back to front again.

Screenshots Here I press cmd + h to hide the radio app, then I change space and come back to the initial space again, then I show the radio again and windows will not re-align. I think change the space a final time, this will fix the issue temporary until I hide again: 2022-01-27 6 51 34 PM

Versions:

Debug Info

$ /Applications/Amethyst.app/Contents/MacOS/Amethyst --debug-info
Version: 0.15.5 (92)

OS version: Version 12.1 (Build 21C52)

Screens:
    (0.0, 0.0, 2048.0, 1280.0) [(0.0, 0.0, 2048.0, 1280.0)]

Configuration:
window-margin-size: 5
window-resize-step: 5
use-canary-build: 0
floating-is-blacklist: 1
float-small-windows: 1
window-minimum-width: 0
window-margins: 1
enables-layout-hud: 1
mod2: (
    option,
    shift,
    control
)
floating: (
        {
        id = "com.apple.finder";
        "window-titles" =         (
        );
    }
)
ignore-menu-bar: 0
debug-layout-info: 0
mod1: (
    option,
    shift
)
screen-padding-bottom: 0
new-windows-to-main: 0
enables-layout-hud-on-space-change: 0
layouts: (
    "tall-right",
    wide,
    column,
    "two-pane",
    "middle-wide",
    bsp
)
screen-padding-right: 0
mouse-follows-focus: 0
mouse-swaps-windows: 1
mouse-resizes-windows: 1
smart-window-margins: 0
screen-padding-top: 0
screen-padding-left: 0
focus-follows-mouse: 0
follow-space-thrown-windows: 0
window-minimum-height: 0
restore-layouts-on-launch: 1
marty@Martins-MacBook-Pro ~ $% /Applications/Amethyst.app/Contents/MacOS/Amethyst --debug-info
Version: 0.15.5 (92)

OS version: Version 12.1 (Build 21C52)

Screens:
    (0.0, 0.0, 2048.0, 1280.0) [(0.0, 0.0, 2048.0, 1280.0)]

Configuration:
window-minimum-height: 0
screen-padding-right: 0
mouse-follows-focus: 0
mod2: (
    option,
    shift,
    control
)
screen-padding-top: 0
window-resize-step: 5
restore-layouts-on-launch: 1
new-windows-to-main: 0
window-margin-size: 5
layouts: (
    tall,
    wide,
    "tall-right",
    "middle-wide"
)
enables-layout-hud-on-space-change: 0
screen-padding-left: 0
follow-space-thrown-windows: 1
mouse-resizes-windows: 1
floating-is-blacklist: 1
focus-follows-mouse: 0
ignore-menu-bar: 0
window-minimum-width: 0
float-small-windows: 1
debug-layout-info: 0
mod1: (
    option,
    shift
)
enables-layout-hud: 1
mouse-swaps-windows: 1
floating: (
        {
        id = "com.apple.finder";
        "window-titles" =         (
        );
    }
)
use-canary-build: 0
window-margins: 1
smart-window-margins: 0
screen-padding-bottom: 0

Additional context The animated GIF above illustrates the wrong behavior when hiding an application, but it acts the same for minimizing windows.

sxg commented 1 year ago

I'm experiencing this exact issue a year later still on Amethyst 0.16.0 (94) and macOS Ventura 13.1. This is a significant issue that happens very commonly and reliably as described above.

SebastianGoeb commented 1 year ago

Any progress on this?

sortega commented 7 months ago

I'm experiencing the same problem consistently. Any plans to act on this bug?