Stable monitor assignment when there's multiple copies of the same monitor #1159
Replies: 2 comments 6 replies
-
If you find how to retrieve it in Swift, I'm ok to add matching by uid like this: [workspace-to-monitor-force-assignment]
1 = { monitor-uid = 178131 } AeroSpace uses https://developer.apple.com/documentation/appkit/nsscreen/. I don't see a way to get UID from But please make sure that they are stable; otherwise, it's all for nothing. Alternatively, I can suggest the following: [workspace-to-monitor-force-assignment]
1 = { monitor-pattern = 'pro display xdr', first-in-sorted-by = 'monitor-min-x' }
2 = { monitor-pattern = 'pro display xdr', last-in-sorted-by = 'monitor-min-x' }
Along with Along with |
Beta Was this translation helpful? Give feedback.
-
@nikitabobko does what you described above work with latest aerospace? or would that be an enhancement?
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to use
workspace-to-monitor-force-assignment
to keep certain windows on my vertical display; but it keeps getting shuffled onto another display during reboot.)=
At the moment, whatever 'name' Aerospace gets for attached monitors seems to be something assigned by the system at boot; and that assignment seems to be mutable. (Sometimes, my left monitor is named “Pro Display XDR (1)” and my right is “Pro Display XDR (2)”; other times they're shuffled in another way.)
Would it be possible to match on another property of the monitor that is more immutable? I see an OS UID (although for all I know that'd also be unstable) as well as the display's serial number as potential options.
(To be clear, this is an issue without
workspace-to-monitor-force-assignment
configured at all; I'm trying to useworkspace-to-monitor-force-assignment
to work around it. The best improvement would be Aerospace transparently handling monitor-location-and-identity more in a more stable fashion; but I don't see how that's possible without user-input.)Additional situations where this presents (some more annoying than others), as search-result keywords:
Disconnecting/reconnecting a display. This is the worst one for me; one of my monitors fully turns itself off every time the input appears/disappears, which plays poorly with macOS display-sleep and Aerospace - it means all of my windows get shuffled every time my computer locks!
Rearranging in the macOS “Displays” settings. Every single one-pixel adjustment of the displays seems to result in the name-assignment by macOS getting reshuffled; it's bad enough that I have to quit Aerospace before messing with the display-arrangement; otherwise all of my windows are randomly shuffling between the displays (including the display-settings window I'm trying to interact with!) every three-to-five-seconds. Oof! (This one isn't so bad during everyday use, though; hopefully one shouldn't have to rearrange their display-settings too often.)
Rotating a display that supports automatic OS rotation, like Apple's XDR. This might suck for users who rotate their displays often; but that's not me right now.
(=
Beta Was this translation helpful? Give feedback.
All reactions