Skip to content
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

Drag window to another screen is not visible anymore #506

Closed
rdewolff opened this issue May 4, 2020 · 6 comments
Closed

Drag window to another screen is not visible anymore #506

rdewolff opened this issue May 4, 2020 · 6 comments
Labels
bug Something isn't working

Comments

@rdewolff
Copy link

rdewolff commented May 4, 2020

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 ?

@koekeishiya
Copy link
Owner

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 #402 (comment)
I have not tested this.

@koekeishiya koekeishiya added the undetermined Not sure if this is considered a real bug label May 9, 2020
@dominiklohmann
Copy link
Collaborator

@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.

@rdewolff
Copy link
Author

rdewolff commented May 9, 2020

Have you been able to reproduce the error? What can I do to help?

@koekeishiya
Copy link
Owner

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.

@rdewolff
Copy link
Author

rdewolff commented May 9, 2020

Okay that's out of my knowledge :P

@koekeishiya koekeishiya added bug Something isn't working and removed undetermined Not sure if this is considered a real bug labels May 9, 2020
@koekeishiya
Copy link
Owner

Fixed on master. Requires the scripting addition to be reinstalled due to a necessary change.

@koekeishiya koekeishiya added addressed on master; not released Fixed upstream, but not yet released and removed addressed on master; not released Fixed upstream, but not yet released labels May 9, 2020
unrevre pushed a commit to unrevre/yabai that referenced this issue Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants