[DESK-5938] revamp WHM → WindowCoordinator, implement eclipsing coordinator & defaults#10
Conversation
DESK-5938 imessage: reactions don't work if the Messages window isn't on the main space
|
There was a problem hiding this comment.
@KishanBagaria i opted to nuke the old spaces code, but we'd actually want that for backwards compat right? i'm not aware of the exact version ranges that it works w/
|
|
||
| static func registerDefaults() { | ||
| swiftServer.register(defaults: [ | ||
| "BEEPWindowCoordination": true, |
There was a problem hiding this comment.
can these keys be in an enum so it's easier to access? why the BEEP prefix?
There was a problem hiding this comment.
why the BEEP prefix?
oh, i can remove, but defaults keys are technically "global" in the sense that the suite name is just a search area. what i mean is that you can do yarn dev -BEEPWindowCoordination NO in beeper-desktop-new and it'd have the same effect as having compiled with NO_SPACES, basically. it searches the cli args before the suite
yea it should work w the macOS 14 |
slice
changed the title
WindowCoordinator, implement eclipsing coordinator
slice
changed the title
WindowCoordinator, implement eclipsing coordinatorWindowCoordinator, implement eclipsing coordinator & defaults
…dow` the latter opens the window
2 participants
Apple has blocked us from using
CGS*/SLS*private APIs, which we were using to punt the Messages app to an offscreen space whenever we needed to automate it. Since we can't do this anymore, we can opt to hide the app, but briefly unhide it behind the Beeper window whenever automation is needed (e.g. for reactions).