hs.spaces #114
hs.spaces #114
Conversation
|
Hmm, I know I said "yes" to spaces, but I don't think I'd quite appreciated the caveats around different OSX versions and precise configurations of Spaces. I'd like some more opinions - do people think we should land this anyway? or maybe use it as the first case of needing to host an extension externally (thus forcing us to tackle #6)? |
|
Perhaps we could check https://developer.apple.com/library/mac/Documentation/Cocoa/Reference/ApplicationKit/Classes/NSScreen_Class/index.html#//apple_ref/occ/clm/NSScreen/screensHaveSeparateSpaces and refuse to do anything if it's enabled? |
|
Yeah, I was thinking about that... let me see if I can get a handle on the exact nature of the oddities and see if they can be enumerated and understood... what I recall myself was that it was correct on the count and with which screen you were currently on, but that moving a window to another space either didn't work (if the space number corresponded to a different physical display) or would move the window and active space, but "out of sequence", in the sense that if you used the mouse gestures or keyboard commands to switch spaces, you bounced back to where you were (previous space) rather than where you were in the cycle (i.e. if I was on space 1, moved a window to space 4, then used a gesture to change to space 3, I jumped back to 1 instead.) Others implied other weirdness with some windows not moving at all, but I never did hear whether they had multiple monitors or this checkbox enabled, so... And there is no way at present (that I know of) to tell in advance what space numbers belong to what physical displays, so it either works or it does nothing. I've avoided using it since it came out in Hydra, and I would have skipped it in Mjolnir for the time being, except it was specifically asked for, so at least some are ok with it's limitations at present. But I do want something... I'm following some others who are using eventtap to trigger the keyboard commands to utilize spaces, and it seems much more consistent, not disrupting the flow, but I think this requires a certain setup under the Keyboard shortcuts, so we'll want someway to check this, and maybe set it ourselves, if the user approves... I don't know. Spaces are a hot item but one that Apple has made a pain in the ass to work with. I don't know if we're better off including what we have but with warnings or take Degutis's approach in his latest faq (https://github.com/sdegutis/mjolnir#faq https://github.com/sdegutis/mjolnir#faq)... I'd rather not go that route, but it's not exactly wrong -- anything anyone does (that I've seen so far) is a bit of a hack.
|
|
Code base removed (thus pull would fail now anyways), but source will be made available as third party extension in case someone wants to play with it later. |
No description provided.