On my work Mac, it isn't working after 0.17.1 #1819
-
|
Steps to reproduce:
Expected result: Stuff tiling correctly Actual result: Windows only tile e.g. after a focus command, also when I close windows, their space stays occupied. Tiling issue screencast here: https://github.com/user-attachments/assets/5745a763-3035-4ba8-bcea-09f3dc17c015 Anyone seen this before? What can I do to make this work? Tried removing and re-adding Aerospace to the accessibility list, but no change.. The same configuration (dotfile-wise) on my personal Mac works just fine (also same OS version etc) ... is there some software from my company interfering? I don't get it. Would be really nice to have the speed updates from 0.20.0 on my work device as well 🥹 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Do you mean same AeroSpace version works fine on your other mac? I suspect that you hit this bug: #1615 One of the other applications is hanging, and it hangs the whole system. Try quitting apps one-by-one to see which one it is (you can start from the most suspicious in cmd-opt-esc menu and/or Activity Monitor) As far as I know, AeroSpace 0.18.5-Beta wasn't affected by #1615 as badly, so you might consider downgrading to 0.18.5-Beta until #1615 is fixed |
Beta Was this translation helpful? Give feedback.
-
|
Yes, on the other mac it's always been fine. Now, after I quit some "Python" process from cmd-opt-esc, it seems to be resolved - I wonder why this persisted throughout restarts. Whatever though, perfect, thank you so much! Update: it is obviously related to an pyautogui app that I was using. Will look for an alternative to that. |
Beta Was this translation helpful? Give feedback.
Do you mean same AeroSpace version works fine on your other mac?
I suspect that you hit this bug: #1615 One of the other applications is hanging, and it hangs the whole system. Try quitting apps one-by-one to see which one it is (you can start from the most suspicious in cmd-opt-esc menu and/or Activity Monitor)
As far as I know, AeroSpace 0.18.5-Beta wasn't affected by #1615 as badly, so you might consider downgrading to 0.18.5-Beta until #1615 is fixed