Michael Tsai and Jason Snell brought it to my attention that Default Folder is almost 30 years old. I guess that makes me a stubborn old man at this point…
Here’s the latest beta version of Default Folder X, including a workaround for a High Sierra bug that caused Default Folder X to beachball for tens of seconds when displaying folders with lots of items in them. It also fixes a problem with “Save as PDF” dialogs not being recognized, along with correcting some graphical glitches.
For folks not using High Sierra, this build also corrects a bug that caused Default Folder X to add duplicate tags to a file when you used the tagging field that’s built into macOS Save dialogs:
A new public beta version of Default Folder X is up on the Beta Testing Page. It’s got fixes for a couple of quirks in the latest High Sierra betas, and also tweaks the UI a bit to deal with the slightly different alignment of things in 10.13.
I’ve also implemented a suggestion that may help to clarify one behavior of the Finder-click feature. DFX offers the option to make Finder-click take you to the Desktop if you click anywhere besides on a Finder window. When this option is turned on, it highlights the entire screen in gray when you move the mouse over any area that doesn’t contain a Finder window – that sort-of reflects that you’re hovering over the Desktop, but often confuses people (the “why is my entire screen gray?” question).
So now the highlighted area will show the non-Finder-window area of the screen in gray – ie. the entire screen minus “holes” where any Finder windows are located. It makes sense, but still looks a little odd to me, so I’m wondering what our non-developer users will think. Does it help? Or is it just weird and ugly? Let me know (I’m sure you will 🙂 )
I’ve just posted a beta version of Default Folder X 5.1.6 that supports the developer release of High Sierra, which Apple made available on Monday. A few under-the-hood changes to file dialogs had an impact on Default Folder X, and we’re still testing to make sure that there aren’t any hidden gremlins. If you run into any issues with the beta, please make sure to tweet, email, or comment here to ensure your bug gets fixed!
Also in the 5.1.6 beta is a handy little enhancement for people that use a consistent folder hierarchy to store files for their clients or projects. You can now use a relative path as a Favorite in Default Folder X. So if you’ve got lots of folders that look like this:
You can set a Favorite for “../images”, for example. Then, if you’re in a Save dialog pointing to any “html” folder, that Favorite will take you to the adjacent “images” folder. Pretty cool for all you super-organized folks 🙂
TLDR; Get Default Folder X 5.1.5 here. Default Folder X now shows its bezel around minimized Save dialogs and fixes crashes and compatibility problems, especially with old Carbon apps like Office 2011 and Adobe Creative Suite 6. It also addresses issues with particular shortcut key combinations and works better with Spaces.
For Those That Want Details: ‘Minimized’ Save As dialogs have been a problem for Default Folder X for some time. Because of the way macOS El Capitan and Sierra work, DFX can’t provide all of its features in a Save dialog if there’s no list of files and folders. Up until now, Default Folder X would simply not appear next to minimized Save dialogs. This caused confusion, with some people thinking that DFX wasn’t working at all, when in fact it just couldn’t do anything in that particular situation.
I kept revisiting this issue over and over again to see if I could find some sort of technical solution that’d let me get Default Folder X working in this configuration. Alas, it’s not to be – there are some fundamental limitations that prevent Default Folder X from working. So in version 5.1.5 I’ve put together a simple bezel that comes up around minimized Save dialogs and offers a single option: expanding the dialog so that Default Folder X can provide all of its features. It isn’t ideal, but it’s less confusing than just having Default Folder X missing in action when you click the minimize button in a Save dialog.
In addition to this change, Default Folder X 5.1.5 addresses a number of compatibility and stability issues (ie. bugs). I’m actually very happy to have found the source of a recurring crash that I’ve never been able to reproduce. Crash logs have been trickling in, but none of them actually pointed to the underlying problem. I’ve now found a bug that appears to be the cause of those crashes, and have also addressed bunch of other issues that have come up since the last release.
A change list and download links are available at http://www.stclairsoft.com/DefaultFolderX/release.html
With today’s release of App Tamer 2.3.2, you can now resize App Tamer’s window to display more processes on larger monitors. This version also fixes a couple of nagging bugs that could cause App Tamer to think it was slowing down a background process when it actually wasn’t. If you’ve ever looked at the process list and seen a background daemon pegged at 100% even though App Tamer shows its yellow “slowed down” icon next to it, this release will fix that 🙂
The 2.3.2 update is free for licensed users of App Tamer 2.x. You can see the detailed release notes and download it on the App Tamer release page.
Version 5.1.4 of Default Folder X is out, and although this update doesn’t bring any big feature additions, it offers a bunch of internal improvements that make things more reliable. If you’re already using Default Folder X, just select “Check for Updates” from the Default Folder X menu in your menubar to get the new version.
And if you’ve experienced a crash in Default Folder X and submitted a crash log after it happened, thank you for taking the time to do so. That data really does help track down problems and get them fixed! If you’re having a problem that doesn’t result in a crash, contact us using the Tech Support page and we’ll do our best to get the issue resolved, whatever it happens to be.
Default Folder X was mentioned on Dave Hamilton’s excellent Mac Geek Gab podcast. It made me laugh so I have to share it. At the end of the segment Dave says “Using a Mac without Default Folder feels like using a Mac with mittens.” I think that’s one of the best endorsements I’ve heard in a while 🙂
Anyway – check it out – along with lots of other great information and commentary – at the 1:20 mark of Mac Geek Gab 647. I think I learn something new in every episode.
While Jettison and HistoryHound are still supported and sold on the St. Clair Software website, I’ve pulled them from the Mac App Store. The versions that were in the Mac App Store were older revisions, and it just didn’t make business sense to rearchitect the apps to meet Apple’s current requirements for approval so they could be kept up-to-date.
For both applications, complying with Apple’s sandboxing and feature constraints to get them approved for sale would have required significant rewrites. And in Jettison’s case, it would also require that buyers download a separate helper app to enable its full functionality. I realize that some people will be put off or inconvenienced by the fact that these apps are no longer in the Mac App Store – my apologies if you’re one of those folks, but it just doesn’t make sense for Jettison and HistoryHound.
Without going into a full-on rant about the Mac App Store (I could ramble on for days), let’s just say that while the Mac App Store is convenient for consumers, it doesn’t really serve the needs of some developers. Much has been written about it already (here, here, here, here and here, for example) so I won’t rehash it all – and despite years of “constructive criticism” from developers, Apple hasn’t fixed some major problems.
I hope you’ll continue to purchase our applications, as well as those from other independent developers selling outside the Mac App Store. While it’s a little less convenient than the Mac App Store, it allows us to bring you the best software we can, and also gives us the opportunity to foster a two-way relationship with you – both of which really matter to us.
Version 2.3.1 of App Tamer fixes several bugs in our CPU- and battery-saving application, as well as more smoothly supporting Spotify. If you’ve got App Tamer set up to manage Spotify’s CPU usage, it will not slow it down or stop it while Spotify is playing music. This prevents your music from stuttering or going completely silent – generally a good thing 🙂
You can find more details and download links on the App Tamer Release page. We recommend that all App Tamer users update even if you don’t use Spotify because the bug fixes are important.
And on the topic of App Tamer, I was remiss in my duties – I didn’t blog about the release of version 2.3, even though it delivered a couple of very significant changes. The most obvious one is a user interface overhaul that brings App Tamer up to snuff with the flat, white look that’s all the rage (check it out over on the right there). The preferences have also been split among multiple tabs to better organize them, and hopefully make all the settings a little less intimidating.
A more interesting, though much less visible addition is App Tamer’s new “CPU hog detection” feature. In the “Detection” tab of the preferences, you can set a limit to how much CPU any application should use. If any app uses that much CPU for longer than a time you specify, App Tamer will pop up a warning to let you know that something’s amiss, and will give you several options. If you’re on a laptop, this is great because it lets you know before the CPU hogging app drains your battery down to nothing and you realize that you left your power adapter under the couch at home.
And of course there are a whole bunch of little fixes and improvements rolled into versions 2.3 and 2.3.1 as well. It’s worth the trouble to download, especially if you’ve already bought a license for App Tamer 2 because these updates are free.