Comments
-
Greg Hurrell
Thanks for the report, Garth. First up, you should try with the version 3.1 release candidate. It's not up on the main website yet, but it has been seeded to beta testers. You can find a link to it in bug #139 (that bug is about fixing Tiger compatibility, but you should grab that version anyway to be sure you are using the latest code).
I do suspect that the problem isn't confined to any specific version of WinSwitch though. I am fairly sure that what you are reporting is actually a duplicate of bug #161. I think there is a conflict with other third-party menu extra enablers.
Once you've installed the new version, if you see that it doesn't activate properly can you try a manual activation? You would manually activate like this:
1. Navigate to /Library/Menu Extras/
2. Using the contextual menu do a "Show package contents" on the WinSwitch.menu bundle.
3. Inside the bundle at "Contents/Resources" double-click on the "MenuCracker.menu" bundle.
4. Now double-click on the WinSwitch.menu bundle itself.
These actions approximate (but not exactly) the actions taken by the installer and activation scripts. The end result should be that WinSwitch appears in the menu bar. You can then Command-drag it over to the right (or wherever you want).
I am going to close this bug and ask that you file any further comments against bug #161. Can you please let me know how you go with the manual activation, and also if there are any interesting messages printed in the console (as was the case with the person who filed bug #161)?
- ** This bug has been marked as a duplicate of 161 ***
-
Greg Hurrell
Marking as CLOSED.
Add a comment
Comments are now closed for this issue.