March 31st, 2014 by Jon
Several people have reported that folders that they’ve put in the Favorites section of the sidebar in Finder windows just disappear, and have thought that either Default Folder X or Jettison was at fault. I’ve confirmed with Apple that this is a known bug in Mac OS 10.9.2. It’s not caused by Default Folder X, Jettison or any other 3rd party application. It’s an issue that Apple needs to fix in OS X.
Here’s a more complete description of the problem:
If I drag a folder to the Finder sidebar to add it as a Favorite, then later eject the disk containing the folder, the Finder deletes the folder from the sidebar. It doesn’t return when I remount the disk.
Steps to Reproduce:
- Plug in an external drive (I used a FW800 drive, but apparently any old disk will do).
- Open a Finder window, navigate to the external drive and then drag a folder from the drive to the Favorites list in the Finder window’s sidebar.
- Eject the external drive.
- Run Disk Utility and remount the external drive.
I would expect the folder to stay in the Favorites list in the sidebar, regardless of the availability of the disk. If I click on it it should ask for the disk or try to remount it automatically. Failing this, if the folder is going to be hidden in the sidebar because the disk is unavailable, it should reappear when the disk is available again.
The folder is removed from the Favorites list in the sidebar, never to return.
March 28th, 2014 by Jon
App Tamer 2.0.2 is available now, providing fixes for a couple of bugs, as well as some minor changes to the UI that help to show what’s going on.
First the fixes:
- In certain situations, App Tamer 2.0.1 could crash when you launched it. This was due to a bug in the way it tracked subprocesses. The common example was a command in Terminal that ran a couple of other commands which in turn spawned subprocesses themselves. A few simple checks were all that was needed to fix it.
- A more common problem was that App Tamer would occasionally stop limiting the CPU usage of an application it was supposed to be managing. This turned out to be a timing issue: If App Tamer stopped throttling a process and then immediately started again, the original CPU limiter would still be winding down and App Tamer would find it and use it rather than creating a new one. A few milliseconds later, that CPU limiter would finish shutting down and disappear, leaving the managed application free to use as much CPU as it wanted. App Tamer doesn’t do that anymore
The UI enhancements:
- Mark Mackay, an App Tamer user in New Zealand, pointed out that if App Tamer wasn’t limiting the CPU use of an application at the time (because that app wasn’t doing anything) he couldn’t tell if he’d configured App Tamer to slow it down. He suggested I enhance the status indicators that App Tamer puts next to each application to somehow show that running apps – the ones with blue squares – had settings attached to them. A little triangle of color in the bottom right corner now shows you if that app will be slowed down or stopped (with yellow or red corners, respectively).
- Version 2.0.2 also dims the icon and name of any application or process that can’t be stopped, so you know not to bother clicking on them.
Grab your copy from the App Tamer Release page. The update is free if you’ve bought App Tamer 2!
February 26th, 2014 by Jon
February 7th, 2014 by Jon
It’s come to our attention (after about a week’s worth of debugging) that a software package called Elite Keylogger Pro disables Default Folder X. The Default Folder X Helper application will still run and you’ll see Default Folder X’s icon in your menubar, but none of its controls will appear around your Open and Save dialogs.
The frustrating problem has been that Elite Keylogger Pro actually hides itself so that it can be installed on a computer and surreptitiously record keystrokes and screen snapshots without anyone knowing (yes, that’s pretty sketchy). When I started receiving bug reports saying that Default Folder X had suddenly stopped working, the System Information reports, Console logs and other debugging information that I got from affected users showed no clear clues as to what was causing the problem. Finally, one observant Default Folder X user (with a good memory) remembered buying Elite Keylogger Pro as part of the Mac Bundle 4.0 and installing it (thank you Adam Olson!)
So, if Default Folder X has suddenly stopped working on your machine, see if you bought the Mac Bundle 4.0 recently – or purchased Elite Keylogger Pro separately – and installed it. If so, this is probably what’s causing the problem.
To get Default Folder X working again you need to uninstall Elite Keylogger Pro. And be careful – you must uninstall it according to WideStep’s instructions http://help.widestep.com/how-to-uninstall-elite-keylogger-mac/. Using a “clean up” application or just throwing the application in the Trash is not enough to remove it from your system.
I’ve contacted WideStep to see about fixing or working around the conflict and will update this as I have more information. Sorry for the trouble and for any time you’ve wasted troubleshooting this (hopefully you haven’t killed an entire week like I have…)
Update: WideStep has issued an update to Elite Keylogger Pro to fix this problem. Get version 1.2.027 or higher from their website to ensure that Default Folder X runs correctly with their software.