Nikita Bobko

Thanks for the report! It looks like it fails somewhere here https://github.com/nikitabobko/AeroSpace/blob/0ce757b/src/mouse/moveWithMouse.swift#L77 when you move the window with your mouse But I don't understand yet why it fails. The code...

It'd be helpful if you could capture the apps/windows you mention with screenshots to understand what heuristics could be applied Additionally, it'd be helpful to capture windows of these apps...

@mike1808, unfortunately, you captured the accessibility properties of some UI element inside the window, but not the properties of the window itself. But it's a common mistake You can use...

Close because of lack of activity. I need `debug-windows` output and screenshots since I don't use these apps. Besides, some apps may already be accidentially supported because dialog heuristics has...

If you want to do only the initial assignment you can do that in `after-startup-command` ``` after-startup-command = [ 'workspace 1', 'move-worspace-to-monitor --wrap-around next', 'workspace-back-and-forth', 'workspace 2', 'move-worspace-to-monitor --wrap-around next',...

**(1)** The reason why I implemented workspace to monitor assignment in a force style is because the assignment acts like an invariant that always holds. Invariant is a good mental...

The most generic solution for **(3)** is to provide one more "basic block" -- `on-monitor-configuration-changed` callback This way, users can reuse their workspace to monitor "initial" assignment script in `on-monitors-configuration-changed`...

AFAIK it's a bug in Apple accessibility API. If not mistaken, I saw the special workarounds in yabai and/or Amethyst. But right now I can't find it in their codebases...

Should be fixed in 0.11.1-Beta It'd would be cool if somebody can confirm

@alexnguyennn thanks for checking! I confirm that the problem is still reproducible with 3 monitors. I normally use 1-2 monitors, and the problem appears to be fixed only for 2...