HyperSpaces - what does it do when there is no DOCK loaded?
Is there any default behavior for when, despite spaces being set up in Hyperspaces prefs, the actual DOCK is not (quite) loaded (yet)?
I use another app (DockSpaces) that loads a unique dock per Space.
Sadly, your latest versions do not play nicely together. In this latest version, DockSpaces occasionally drags its feet when loading a dock. Im not sure what the problem is.
They used to work just fine. I am sure much has changed under the hood in the new version.
So I ask: if Hyperspaces does not find a dock loaded, does it reach out and grab one from Dock.app? Because if so, when it does, it is KILLING all of the dock-space-application bindings i have set up.
And NUKING all my other customizations to the current dock. This requires a very elaborate work around on my part.
I guess this could be an OS response to no dock being loaded.
Any help would be dearly appreciated.

Support Staff 2 Posted by Tony Arnold on 28 Jun, 2011 02:04 PM
OK — so Spaces is actually part of the Dock, so I'm pretty sure that Hyperspaces won't work at all if the Dock isn't loaded.
What you're probably seeing is the system itself (at the behest of Hyperspaces) grabbing the Dock in between reloads — the way that DockSpaces works is neither safe, nor something that Apple would approve for the App Store (brute force reloading the Dock process and changing out it's preferences while the process starts again). There's no way for an app like Hyperspaces to work and not interact with the Dock process in some manner.
Unfortunately, I've never been able to find a good way to prevent Hyperspaces from interfering with the way DockSpaces does it's work.