-
Notifications
You must be signed in to change notification settings - Fork 487
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
Ability to throw window to next/prev screen #1666
Comments
Isn't this what "Throw focused window to space left" and "Throw focused window to space right" do? I might be misunderstanding, but those do what you describe. On that note, since my update to MacOS |
Not work for me too : ( |
Looks like this has been fixed already, I had to reinstall Amethyst though (ala |
Oh wow, thank you for that hint @phillipvanheerden. Reinstalling did the job for me, after spending a lot of time trying to figure out what went wrong. |
Throw to screen is not throw to space. Space is like a desktop, but screen is like a monitor on your MacBook. |
interestingly, that did not work for me - but seems to have worked for some others. |
this worked for me after struggling with this for weeks, thank you so much! |
Throwing windows to other spaces still doesn't work for me after updating to Amethyst |
Is your feature request related to a problem? Please describe.
Searched for:
And I got nothing. So seems like not related to any others.
Describe the solution you'd like
Now we have throw window to screen 1/2/3/4. I want Amethyst get the ability to throw window to next/prev screen.
I should give some cases to help you guys get what I mean. Above all, let's assume that we have 3 monitors.
case1: on screen 1, throw to next screen, expect throwed to screen 2;
case2: on screen 2, throw to next screen, expect throwed to screen 3;
case3: on screen 3, throw to next screen, expect throwed to screen 1;
case4: on screen 1, throw to next screen, expect throwed to screen 3;
Describe alternatives you've considered
None.
Additional context
None.
The text was updated successfully, but these errors were encountered: