The title says it all, when I use the shortcut to drag a window, if I move it to another screen, my windows is not visible and hard to recover.
Is this a known issue ? Any fix or workaround ?
Hmm I was not actually aware of this behaviour. We are using a private macOS API to move windows around, and the call is literally just MoveWindow(id, x, y);. I have an idea of what is missing, but I need to do some digging around for this. There isn't a workaround that i know off.
@dominiklohmann mentioned a native way in macOS do achieve the similar move-window functionality here https://github.com/koekeishiya/yabai/issues/402#issuecomment-582471340
I have not tested this.
@dominiklohmann mentioned a native way in macOS do achieve the similar move-window functionality here #402 (comment)
I have not tested this.
I actually prefer this way, because it's a lot smoother and I tend to use ctrl + cmd as my modifier keys for yabai mostly anyways, but be aware that the keyboard shortcut for this cannot be changed and that other than yabai this actually raises the window.
Have you been able to reproduce the error? What can I do to help?
I can reproduce the issue yeah. So to resolve this we basically need to reverse engineer the NSWindow code in the AppKit framework to see what happens internally when a window is positioned. I think I have a lead, but I have not yet attempted to dig into it.
Okay that's out of my knowledge :P
Fixed on master. Requires the scripting addition to be reinstalled due to a necessary change.
Most helpful comment
Fixed on master. Requires the scripting addition to be reinstalled due to a necessary change.