-
Notifications
You must be signed in to change notification settings - Fork 485
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
Unable to throw window to spaces left or right #1655
Comments
Same for 0.21.1 (111) (homebrew installed) on macOS 14.5. |
Duplicate of #1643 ? |
Only if someone reopens it. Throwing a window on 0.21.1 still doesn't work on 14.5; something definitely happens b/c I can see the rolling flicker as all windows redraw, but the target window doesn't move. |
seeing same behaviour as Cerebus |
also happens for me with homebrew build, will try with github release page one. They should be the same though no? |
I also have this issue, but I'm on an M1 MacBook Air |
This issue arose immediately following Mac OS X update to Sonoma 14.5 (it also botched up several utilities like sed). Not only "throw left and right" but all "throw" (to any named/numbered desktop) is broken. |
To be clear: This is on Macbook Pro 2017, so that's Intel Core i7. |
Updated the ticket info to track the issue on Intel. |
I'm on an M2 Mac, and am also experiencing the issue. This also occurred for me after an OS upgrade to Sonoma 14.5, so perhaps it's tied to OS version? |
I am an M1 mac user as well, same issue. It is not an intel-specific issue it seems. |
Interesting! I'll try to look deeper. |
I'm also having this issue on an M2 macbook air (Sonoma 14.5). Amethyst version 0.21.0. |
Same thing happens for me after the most recent MacOS update. Running on a system patched with Open Core legacy patcher, if that matters, but all worked fine before the MacOS update. Tried to change to other hotkey combo, but same results. The active window just flickers and doesn't change space. There are some console messages from Amethyst reading "[0x7ff13f006ea0] Channel could not return listener port." Don't know if might somehow be related. Please let me know if I could help in debugging somehow. |
Hi, I've been having the same problem. I've found that it's related to full screen apps. At least in my case. When full screen apps are on the "right" side in Mission Control, everything works fine. But when I move the "with mouse from Mission Control" full screen app to the left, it stops working. Eg. when first "space" is fullscreen app, from Mission Control perspective, then throwing does not work. I'm using an M1 CPU, macOS 14.5, and Amethyst 0.21.1. |
+1 |
All my spaces are in 3-column middle, and I rarely (if ever) use macOS fullscreen. |
Some further system information:
|
+1. Same for 2019 Intel Macbook pro. Happened immediately after upgrade to Sanoma 14.5 |
I'm running an M1 Macbook Pro 16". Upgraded to MacOS 14.5 last night and experienced the throwing issue this morning. Upgraded Amethyst to 0.21.1 just now and throwing works again--albeit for non-fullscreen apps. As long as I'm using Amethyst to manage windows instead of Mission Control, it works. No offense to others but, if you have Amethyst to manage your windows, why are you still using Mission Control to manage windows? You can easily use Amethyst to accomplish the same effect but better. I never even attempted to use Mission Control for window management ever since I started using Amethyst like 10 months ago so I never attempted to throw a window managed by Mission Control. It's true that it doesn't work for me in 0.21.1, but I never would have known it worked before because I never used it. |
What do you mean by "a window managed by mission control"? |
At least for me, this issue is closed by the 0.21.1 release. |
This is a demo of what I mean by "a window managed by Mission Control". Copied someone else who referred to it that way in their post. But it seems like the correct terminology based on what Mac has called "Mission Control" historically. It is their name for the group of MacOS features used to manage windows. |
With the 0.21.1 version I can throw windows to various spaces again. Thanks for fix 👍🏼 |
Alas. The error persists. It worked on first updating to 0.21.1 but it is back this afternoon. It is not immediately apparent that anything has changed. |
I don't understand your original comment in this context. If we both understand Mission Control as the group of MacOS features used to manage windows, and not some property of a window itself denoting a hierarchy of responsibility, then what do you mean when you say:
All windows are 'managed' by Mission Control. In the sense that those features are built into the OS. In the same way that DWM 'manages' X windows in Linux, even if you decide to use an alternate tiling manager adjacent to it. Are you saying you've never thrown a window to another space? Or are you suggesting that you have thrown windows that were not managed by Mission Control? Maybe you meant you didn't use Mission Control to throw the window to another space? In which, case you were using Amethyst to do this, which is exactly the feature this issue is related to?
What doesn't work for you in 0.21.1? Throwing windows to other spaces? Something else? You say:
What do you mean by 'it works' then? No offense but the comment you posted is egregiously difficult to understand. In any case, the issue seems to be intermittent on my machine in 0.21.1 but is not solved. @ianyh if there is anything else I can provide to assist please let me know. |
I've got 2 macbooks, one intel, one M3, both running 0.21.1. Throwing windows IS working on the M3, which is connected to an external monitor (note, only the external monitor is in use, not the laptop display). Throwing windows on the intel machine, using only the laptop display IS NOT working. I'll do some more testing with/without external monitor, but could this explain the intermittent behavior you're experiencing @nahoskins ? |
Currently, using 0.21.1 I am unable to: I am able to: As far as I can tell the issue is limited to swapping to adjacent spaces. (which is what I use the most, naturally!) It DID work, very briefly, after I updated. It was only able to throw spaces to the right, but it did do that for a short time. Now it does neither left nor right. One interesting note, the render flash, occurs when I try to move spaces left, but not right. And to add, I am using an external monitor (dimensions I believe are listed in the output I posted above). I am not using any full screen apps. |
So when you say 'throw windows' you were referring to moving windows into the left and right splits of the screen is that correct? I at least, do not use full screen or split screen windows with Amethyst. I, like you I imagine, use Amethyst exclusively for managing windows and do not split spaces or use full screen spaces. It sounds like you originally thought the issue was with throwing split spaces or full screen spaces then, I never would have thought to try that. The issue is with bob standard, iterm2 windows not moving to adjacent spaces when I tell Amethyst to do so via the keyboard shortcut designated for it. Let me know if I'm still misunderstanding you. |
OK after uninstalling the homebrew version and rebooting. It appears 0.21.1 DOES throw left and right. This behaviour is then broken when you fullscreen an app. This seems like a separate issue to me. Marking Closed. |
Oh, I hadn't considered brew installations! Could someone who has installed via homebrew confirm for me that the fix is working for them? |
I'm using homebrew (v0.21.1) - doesn't seem to work for me (I'm a recent user, so I haven't used it when it was working - I'm imagining that it should "swap" two windows within a screen?). Also throwing to a specific number (1) only works for a second, then is reversed. |
Specifically, if I have a fullscreen window on my primary display, amethyst is unable to throw windows to adjacent spaces. I've just confirmed the brew install has the fix. I have created a new issue related to the fullscreened windows breaking the adjacent window throw. |
Both my installations are via homebrew. Both installations are running version 0.21.1 (111) M3 Macbook using only a single, external monitor, able to throw a window to space using either throw left/right or throw to a specific space number. Intel Macbook using only the laptop display, NOT able to throw windows. Intel Macbook using only a single, external monitor (same as used with M3), NOT able to throw windows. Here's debug info from intel macbook while connected to external monitor:
|
Same as @douglassd, on Intel Mac, not working. Definitely an additional issue with the full screens, but even without them it doesn't work. Jumps over and then right back again within a second. |
Agreed @roaldarbol , and confirming that I was testing without any fullscreen apps |
I believe you've got what I was trying to say for the most part. I'll separate categories below to more clearly present what I experienced: NORMAL WINDOWS USING AMETHYST FOR SPLIT-SCREEN OR FULLSCREEN LAYOUT
FULL-SCREEN AND SPLIT-SCREEN using Spaces / Mission Control (not amethyst)
|
@ianyh why would there be a difference between the homebrew and the github builds? In my case it's still broken even when using the github build, to be clear I'm not trying to do it with fullscreen windows I got a intel mbp16 from 2019 |
@nahoskins does this still work for you? could you reopen it's definitely broken for some people |
It appears that this is still an open issue, seemingly specific to Intel based Macs, on the 0.21.1 release and 14.5 MacOS |
This issue does not occur on my m3 machine running 0.21.1 (111) I do still have an issue when an app is in 'full screen' mode which I have created a separate issue for #1660 |
This isn't specific to Intel-based Macs. I have a MacBook Pro with M1 Max and am also not able to throw windows since upgrading to Sonoma 14.5 |
have you tried upgrading to 0.21.1? That fixed the issue for me |
Same issue here. I can't throw windows.
|
Trying to upgrade from 0.21.0, Amethyst says I'm at the latest |
You need to enable development builds.😊 |
@ianyh is there anything we could do to help you? (iirc you don't have access to an intel mac), like send some logs etc. |
After an uninstall/install of Amethyst 0.21.1 (111), the 'Swap focused window clockwise' (Ctrl+Option+Shift+k ) worked OK, right after launching Amethyst for the first time. Sonoma 14.5 (23F79) on M2 EDIT: Things started to work for me after (quit Amethyst and) deleting |
same issue here, but only happens when throwing windows to a different numbered space on the same monitor ( intel mac, 14.5). My m1 macs don't have this issue on Sonoma 14.5. |
+1 Apple M2 Pro |
Started having this issue after I updated my MacOS Ventura to 13.6.8 on a 16" Macbook pro M1 Pro. Tried reinstalling Amethyst from the GitHub releases as well as homebrew. Having issues with both. |
same issue with me |
See #1682 |
Describe the bug
A clear and concise description of what the bug is.
Engaging the keys defined for the purpose fails to move windows to spaces to the left or right
Applications:
What applications are involved?
All
To Reproduce
Steps to reproduce the behavior:
Sonoma 14.5
Amethyst 0.21.0 110
Expected behavior
A clear and concise description of what you expected to happen.
The window to be pushed into the adjacent space
Screenshots
If applicable, add screenshots to help explain your problem.
Not applicable.
Versions:
Sonoma 14.5
Amethyst 0.21.1 111
Debug Info
Note:
--include-apps
will list your manageable applications, but is optional if you don't want to list that.Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: