-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
Node is not deleted from the tree when window is closed #653
Comments
I'm experiencing the same issue on macOS Sequoia 15.0.1, however it works fine on Sonoma 14.7.1. I suspect this has something to do with the new Window Tiling feature in Sequoia, but I might be wrong (the tiling toggles are disabled in my preferences pane) |
FWIW I have those tiling options in Desktop&Dock disabled. |
I suspect that Another piece of observation: if I completely close iTerm, so that the app really quits, and then open it again, it will position itself correctly on all available space. |
I got some progress, but I don't know what I'm doing :D
to MacApp.swift, and then call it from gc() on every refresh after |
Duplicate of #445 |
If you lock the screen, all windows attrs becomes empty. You unlock the screen and windows don't preserve their workspace assignment |
Thanks for looking into it @nikitabobko! And for writing this savior of macos that makes it useable! :D So I went to sleep with a release build that had those changes running. It locked the screen because I was away for a long time. There are no logs in that piece of code so I can't tell if it executed it for every window or not, but I can't see any strange behavior from the machine. All windows were on correct monitors. I can manage windows with hotkeys. I tried moving focus on one workspace, jumping to different workspace on the same monitor and to different monitor, resizing windows, moving windows. And then I tried closing a window of iTerm. And it behaved as it should, I didn't notice anything at all. Then I tried locking the screen myself, and I also didn't experience any effects at all. It works.
It says
For me it's every time, very consistently. I don't have to do it quickly. And I don't have to do multiple in a row. It just never fires the kAXUIElementDestroyedNotification. And I also had a breakpoint in the callback there, it was never hit. |
release.tgz
I wonder if that will work for your case also, @juandazapata. |
@mkutsevol if you want to share code, please share links to commits in your fork instead of sharing compiled binaries. |
git diff https://gist.github.com/mkutsevol/bf4567a7e5b7818245847e644965fc55 The meaningful part of the code is above in this thread. I found it to be tedious to get it to compile, setup env. So a binary is useful if folks want to spend 10 minutes testing, not an hour setting up the build env for it. |
After several days with my changes I definitely see that sleeping (logoff) does something to it, as @nikitabobko said earlier. But with my config, where workspaces are pinned to monitors and windows are pinned to workspaces in config, it doesn't matter much. I lose ordering of terminal windows after a break, but that I can live with, compared to the app being unusable for me. So the changes I had are just trading one problem for another, it's not a fix of any kind. I'll sit & wait for a proper solution :D |
Describe the bug
When I close any window, its space is not reclaimed by siblings.
https://youtu.be/5JPp_Tts4tM how it happens for me.
$aerospace list-windows --workspace 5 --format "%{window-id} | %{window-title} | %{app-bundle-id} | %{app-name}"
gives me
This happens for any app, not just the terminal.
But if I have 2 different apps on a workspace, and I close one, it behaves correctly.
I'd expect the ||| split to turn into || split after the middle one is closed.
It doesn't matter which one I close, if it's on the edge or inside. Type of layout doesn't matter also.
Configuration of aerospace is the default one from the docs.
Versions:
aerospace CLI client version: 0.15.2-Beta b6cf827
AeroSpace.app server version: 0.15.2-Beta b6cf827
Displays have separate spaces is disabled.
macOS is 15.0.1 (24A348) running on mac studio 2023 with 3 monitors.
Output of
aerospace debug-windows
I clicked that empty space in the middle. It was a different run of the same reporducer, not the one on the recording.Please help.
Thank you!
Related issues you could find
I failed to find anything. It makes me think that I'm missing something obvious. Please help :)
The text was updated successfully, but these errors were encountered: