turly
08 Dec 2013, 18:47 | FinderPop 2.5.3 BETA
FinderPop 2.5.3 BETA (tagged "Bah, humbug!") is now available.
Note that this is a BETA version, please don't publicise!
INSTALLATION:
Ensure that the System Preferences panel is CLOSED. Quit. Not running. Double-click the FinderPop.prefpane icon. System Preferences will
open and ask if you want to install FinderPop for all users or just you. Choose "All Users" and continue.
2.5.3 Beta has a couple of minor command-line tweaks that some people were asking for. If you don't feel comfortable using the shell, skip this release!
- You can turn off all icons in FinderPop by doing the following and then turning FP off and back on in System Preferences.
defaults write com.finderpop.finderpop useNoIcons true
- You can get FinderPop to partially patch the Finder so that only the clicking-in-unused-menubar stuff works there - i.e. FinderPop will not touch the Finder's contextual menus - by doing
defaults write com.finderpop.finderpop fullyPatchFinder false
Note again that you will need to turn FinderPop off and back on again in System Preferences for "defaults write" stuff to be noticed by FinderPop. This will affect the next time the Finder is patched.
- Thrillseeker alert! If you want FinderPop's click-in-unused-menubar feature to work in Google's Chrome browser, you need to do the following drastic step AFTER you've installed FinderPop for "All Users":
sudo mv /Library/ScriptingAdditions/FinderPopOsax.osax /System/Library/ScriptingAdditions
Note that this is extremely naughty, we are in effect pretending that FinderPop's Scripting Addition ("osax") is an Apple system osax which Chrome will load without question. I have asked the Chrome developers to allow loading of FinderPop's osax without resorting to this skankiness, but - as usual for Google - the request has been ignored. So this is taking matters into my own hands - I should be able to control what runs on my own machine, no? I've been using FinderPop in Chrome regularly for the last couple of months without problems.
FinderPop will figure out where the osax lives and it will be updated or deleted appropriately if you install a new version of FinderPop (or remove FinderPop via the prefpane - FinderPop->Etc. tab->Uninstall FinderPop...)
NB: If you experience Chrome crashes after doing this, it could be that FinderPop is to blame: you can move the FP osax back to /Library/ScriptingAdditions by
sudo mv /System/Library/ScriptingAdditions/FinderPopOsax.osax /Library/ScriptingAdditions
and then restart Chrome. If the Chrome crashes stop happening, it might be FinderPop's fault, in which case tell me about it! If the crashes continue, it's not FinderPop's fault.
The previous beta version of FinderPop is available here (2.5.2).
If you're installing this over a previous version of FinderPop, you'll have to restart or logout/login for it to take effect.
As usual, if there are any issues with this, reply here in the forum! |