It wasn’t clear from your note whether the version you link to fixes a hang, or if it just provides a workaround (pressing grid and waiting up to 30s).
Also, would this version require manual installation, or is it considered the newest default now? I ask because I wonder if I should update all my machines to that .zip or just (more conveniently) hit “check for updates”.
One more thing: Was there ever an issue of the same hotkey in play for both TotalSpaces2 and Mission Control? Which system gets the hotkey, or is it undefined?
Sorry, I should have said that 2.0.15 fixes the hang that I experienced. I’d love some feedback on what happens for you.
You should install it from the zip on the machine you have the issue with. It is not in the general update feed yet. There is a pre-release update feed, and it’s in that one (but the option for that feed is only present in 2.0.15 for the first time, so this time you need to use the zip anyway).
If this version works well, then I’ll update the main feed so that Check for updates would pick it up.
QQ: Was there ever an issue of the same hotkey in play for both TotalSpaces2 and Mission Control? Which system gets the hotkey, or is it undefined?
Ok, I’m running 2.0.15 now, and I’ve reenabled hotcorners in it. I’ll use it heavily today and report back if there’s a problem. If you don’t hear from me, it means all’s good.
In answer to your question, both would receive the hotkey. This is undesirable, but in most cases it won’t matter.
If, for instance, mission control is activated by the same key press as the overview grid, then mission control will get the hotkey first, and the overview grid won’t activate (because that’s not allowed in Mission Control mode).
i’m using the new 2.0.15 and i had a new couple of crashes/frozen interface.
however, this time i had an external monitor close by and managed to ‘unfreeze’ by simply connecting or disconnecting the external display, somehow forcing a display reset.
