-
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
Throw focused window shortcuts not working after MacOS 12.2 upgrade #1192
Comments
Can confirm, same versions of MacOs and Amethyst, the "throw focused window" shortcuts are not working |
Take a look here #1184 |
Hi @ianyh, any chance we could get a new release published with this fix? |
I can confirm this issue. |
Please, release 😭 |
Please! 😅 |
Release it, please. |
Just tried this fix building development branch but unfortunately this issue is still here 😭 |
Lmao I spent like 3 hours on this before realizing wait... maybe its the OS upgrade. AHhhhh |
hi @ianyh, are you actively working on this project? |
Short answer is yes, but my availability is spotty due to other responsibilities. |
It looks like I've fixed the problem locally by using CGSMoveWindowsToManagedSpace instead of CGSAddWindowsToSpaces + CGSRemoveWindowsFromSpaces. |
The development branch build seems to have solved my problem, thanks @dzanotto
|
This puzzles me a bit |
is there already a plan for the next release? Best, |
Added CGSMoveWindowsToManagedSpace ianyh/Amethyst#1192
Moved from CGSAddWindowsToSpaces + CGSRemoveWindowsFromSpaces to CGSMoveWindowsToManagedSpace ianyh#1192
Yes, you're probably right.
I've created a PR for CGSInternal and one for Amethyst. I hope it can help.
This is a good strategy to fix bugs, painful but good 🤣 |
Puzzled me too, I swear it was working for a while after I built it, today its not working again. I edited my comment, you are right its not fixed. |
I recently upgraded to Monterey 12.0.1 and hit this. It seems if I use the keybinding twice to move a window to another space, the second action moves the window. The first key action does something, as I see other windows on the current space adjust - but I haven't had time to figure that out. |
If you build from the dev branch, this has been fixed :) Otherwise you will have to wait for a new release |
@dzanotto the How did you work around this limitation? It's a blocker for my project (https://github.com/lwouis/alt-tab-macos), and I'm curious how you guys dealt with |
I confirm it doesn't seem to move fullscreen windows and TBH I don't even know if Amethyst was ever supposed to do so 😅 |
After upgrading to MacOS 12.2, the 'throw focused window to spaces' doesn't seem to be working anymore.
No error shown, but it just doesn't shift the window to the specified space.
The 'Swap focused window' shortcuts seem to be working fine.
I can still manually shift windows between spaces using the Apple default shortcuts (Click title then ctrl #).
Versions:
MacOS 12.2
Amethyst 0.15.5 (92)
Reproduction:
Using the versions above, set your short cuts for 'throw focused window to spaces', restart Amethyst, attempt to throw a window to a new space and observe it doesn't work.
Debug Info
❯ /Applications/Amethyst.app/Contents/MacOS/Amethyst --debug-info
Version: 0.15.5 (92)
OS version: Version 12.2 (Build 21D49)
Screens:
(0.0, 0.0, 2560.0, 1080.0) [(0.0, 0.0, 2560.0, 1080.0)]
Configuration:
window-minimum-width: 0
screen-padding-left: 0
enables-layout-hud: 0
mouse-swaps-windows: 1
mouse-follows-focus: 1
floating: (
)
mod1: (
option,
shift
)
screen-padding-bottom: 0
window-resize-step: 5
mod2: (
option,
shift,
control
)
layouts: (
tall,
wide,
fullscreen,
column
)
debug-layout-info: 0
screen-padding-right: 0
follow-space-thrown-windows: 0
use-canary-build: 1
float-small-windows: 1
window-margin-size: 0
window-minimum-height: 0
new-windows-to-main: 0
screen-padding-top: 0
window-margins: 0
floating-is-blacklist: 1
enables-layout-hud-on-space-change: 0
focus-follows-mouse: 0
restore-layouts-on-launch: 1
mouse-resizes-windows: 1
ignore-menu-bar: 0
*** Additional: ***
I haven't changed my configuration in any way recently, has been working for 6 months until the update.
The text was updated successfully, but these errors were encountered: