Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Issue moving windows between external displays with mouse #820

Closed
pete-may opened this issue Feb 1, 2021 · 8 comments
Closed

Issue moving windows between external displays with mouse #820

pete-may opened this issue Feb 1, 2021 · 8 comments
Labels
bug Something isn't working

Comments

@pete-may
Copy link

pete-may commented Feb 1, 2021

Hi, I'm having problems dragging windows between two displays with my mouse (from mission control). When I release the window on the new display it snaps back to the original screen. I have to try this 3-4 times before it finally sticks. Any suggestions?

Info

  • Running latest yabai (3.3.6)
  • Running Big Sur OSX
  • Operate in stack mode most of time
  • Do not have the scripting additions (never needed it)
@Vermoot
Copy link

Vermoot commented Feb 13, 2021

Same issue here, on Catalina, bsp mode everywhere and I do have scripting addidions installed.

@JonathanHuot
Copy link

I have the same issue. I found it less prone to errors if we wait a couple of seconds before releasing the mouse button. It seems that when we move a window without dropping it, a preview is done and it might conflict with the actual action when we release the mouse button before the preview is fully displayed.

@koekeishiya koekeishiya added the bug Something isn't working label May 11, 2021
@koekeishiya
Copy link
Owner

koekeishiya commented Oct 19, 2021

I don't think this is something that can be fixed; does this happen if you do not use yabai?

There are already checks in place that are supposed to make sure that we do not react to mouse-actions while mission control is active, e.g: https://github.com/koekeishiya/yabai/blob/master/src/event.c#L635

I did manage to reproduce this, however it was not easy when using a touchpad.

  1. open mission-control
  2. drag a window from one display to another
  3. release the mouse and somehow almost instantaneously exit mission-control
  4. window snaps back in rare cases. in other cases mission-control was exited but the visual transformation applied while mission-control is active did not actually revert (macOS bug).

For me the issue did no longer occur if I simply wait like half a second after releasing the mouse-button on the target display, before exiting mission-control. If this to slow for you, I would suggest just using keyboard shortcuts to move windows between displays.

@koekeishiya koekeishiya added the can't fix Issues are unsolvable label Oct 19, 2021
@Vermoot
Copy link

Vermoot commented Oct 19, 2021

I just gave it a try: This still happens to me (on Big Sur), without having to exit Mission Control quickly.

Stopped yabai, gave it a try: it no longer happens.

koekeishiya added a commit that referenced this issue Oct 19, 2021
@koekeishiya koekeishiya added the-future I never think of the future - it comes soon enough. and removed can't fix Issues are unsolvable labels Oct 19, 2021
@koekeishiya
Copy link
Owner

Did some more digging and turns it was related to some other feature that was meant to help the mission-control integration work properly. This issue has been resolved on the-future branch.

@braham-snyder
Copy link

I think I have a similar, longstanding issue — still present on yabai-v4.0.1. One repro:

  1. Open three windows on a Desktop
  2. Press mission control
  3. Drag two of the windows to an unselected/hidden Desktop on a different monitor
  4. Press mission control again

At this point, one of the windows erroneously returns to the first Desktop.

@koekeishiya
Copy link
Owner

koekeishiya commented Aug 24, 2022

@braham-snyder That issue is fixed on master (at least I am unable to reproduce it using the above steps).

Hm I am able to reproduce now, but it is not consistent.

@koekeishiya
Copy link
Owner

Fixed on master.

@koekeishiya koekeishiya removed the addressed on master; not released Fixed upstream, but not yet released label Aug 24, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants