Loading Profile...
Relaunch problem concerning the Switcher of Hyperspaces
Not new, but still present in version 1.0fc2a, there seem to be a subtle bug in the Switcher.
How to see?
- standard config with 4 Spaces
- run Hyperspaces... use as much as you want... then quit
*BEING IN ANOTHER SPACE THAN #1* (being in Space 3 for instance)
- relaunch Hyperspaces
=> The Switcher is in problem (a part of it thinks to be in Space 1, another part thinks to be in Space 3):
- Background of Space 3 is displayed at relaunch (OK)
- Opening the Switcher highlight Space 3 (OK)
BUT
- Every Spaces, except Space 1, can be selected in the Switcher (not OK)
- Even worse, you can select the current Space 3 itself (nto OK)
This seem to show that a part of the Switcher algorithm thinks the current Space is #1, and not the right #3 that is displayed...
How to see?
- standard config with 4 Spaces
- run Hyperspaces... use as much as you want... then quit
*BEING IN ANOTHER SPACE THAN #1* (being in Space 3 for instance)
- relaunch Hyperspaces
=> The Switcher is in problem (a part of it thinks to be in Space 1, another part thinks to be in Space 3):
- Background of Space 3 is displayed at relaunch (OK)
- Opening the Switcher highlight Space 3 (OK)
BUT
- Every Spaces, except Space 1, can be selected in the Switcher (not OK)
- Even worse, you can select the current Space 3 itself (nto OK)
This seem to show that a part of the Switcher algorithm thinks the current Space is #1, and not the right #3 that is displayed...
I’m confident
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Wow, that's quite odd. I can't replicate the behaviour here - I switched to space 2 using the switcher - quit Hyperspaces - and then relaunched.
The switcher (and the menu) recognised that I was on space 2 and displayed/worked as expected.
Can you reproduce this everytime?
I’m unsure
-
Inappropriate?Very odd you can't reproduce this behaviour since it is possible everytime I quit for me. But I'm not sure we totally understood each other and I'll try to be more precise:
- switch to space 3 (or 4 or 2, but not 1) and quit Hyperspaces as you did.
- if you relaunch Hyperspaces I hope you'll see all this like me:
a) The desktop background of Space 3 reappears: perfect
b) Hyperspaces menu indicates you're in Space 3: perfect
c) The Switcher highlights Space 3 thumbnail (with a grey border): perfect
BUT
d) You cannot select Space 1 with its Switcher thumbnail: problem (it's a reachable space)
e) You can select Space 3 thumbnail: problem (it's the current space!)
After switching to another Space than the two concerned above (#1 and the one you quit, here #3), let's say after switching to space 2, then everything is OK again.
That's why I conclude as above...?
It's worth mentioning that this can be reproduced even if I restarted from scratch after I moved com.thecocoabots.Hyperspaces.plist to the Trash.
By the way, moving this preference list to the Trash surprised me: relaunching Hyperspaces after that displayed a "fresh" configuration, but directly placed in Space 2. Is it really the default space of Hyperspaces? (Maybe to show explicitely to the new user that there is several spaces?)1 Comment
Add a comment
This solves the problem
-
Hi RYann,
Just quickly: no, space #2 is not the default space. Hyperspaces does not default to any one space - it should just pick up which space you're on as it launches. If you activate Apple Spaces, which space does it report you are on? Are you running any other virtual desktop managers at the same time? -
Inappropriate?Oh, how obvious, I forgot that Spaces was of course running too!
That explains clearly the fact that Hyperspaces, without any plist file, was starting directly in Space 2... Simply because Spaces was set in space 2... But that was not so obvious since I am now so used to have different background that my brain is "hard-coded" thanks to Hyperspaces ;-)
Besides this little point of fresh start that is now explained, I can only confirm the little bug in the Switcher that I observe when quitting Hyperspaces from another space than #1 and relaunching.
I cannot describe what I get more precisely than in my previous message, but to answer your questions:
- of course Apple Spaces is running (necessary for Hyperspaces)
- no other app concerning the spaces is running, except "Warp" (which is not really a virtual desktop manager): then I retried without Warp being activated, and the problem is the same.
I hope all this will make you able to see what I mean... and maybe to find the solution.
Maybe other users could confirm or not that they notice the same behavior of the Switcher after relaunching?
I’m confident
-
Inappropriate?I think I understand the "little bug" you described, but I can't reproduce it. I don't believe that Warp is to blame - I know most of the methods being used in that application to work it's magic, and I'd be very surprised if it were interfering with Spaces or Hyperspaces.
In my set-up, I work with three spaces (yes, you could joke that I don't need a license for my own product!).
- I switch to space 3;
- I quit Hyperspaces;
- I relaunch Hyperspaces;
- I activate the switcher using the keyboard shortcut;
- I press the left arrow until space 1 is selected and press enter;
- Hyperspaces lets me select and switch to that space;
How are you selecting the space you want to switch to from the switcher? Via mouse, or keyboard? -
Inappropriate?Oh, yes, you got it!
You're a bit too addict to the keyboard ;-)
1) I can confirm that your own test (detailed above) work for me as well
(in other words: using the keyboard to select a new space in the graphical Switcher)
2) I can confirm (and that is the difference) that using the mouse and click to select a new space in the graphical Switcher give the resulting bug I described.
In short:
- with the keyboard, you can move the white rectangle to any of the spaces.
- with the mouse, normally you can move the white rectangle only to reachable spaces (that is to say all, except the current one). But with the described bug, the only one that is unselectable is always the #1 after relaunch.
So the bug concerns only mouse users!
I’m amused
EMPLOYEE
