I’m happy to announce that the final version 5.4 of Default Folder X is now available. Thank you to everyone who beta tested the pre-release versions and reported issues!
The marquee feature of this release is, of course, support for macOS 10.15 Catalina, which Apple should drop any day now. In addition, there are a couple of new AppleScript commands in Default Folder X’s scripting dictionary to help scripters automate the handling of file dialogs (and don’t forget the scriptable default folders too). This version also adds support for the version of Path Finder distributed via SetApp.
Finally, there are a handful of bug fixes, including corrections for issues with Finder windows, adding new Favorites, and Accessibility quirks. These fixes apply to both Catalina and earlier macOS versions – if you’re running an older version of macOS, you can still update to Default Folder X 5.4. It supports anything from macOS 10.10 to 10.15.
The update is free if you’ve already got a license for Default Folder X 5 – just choose “Check for Updates” from Default Folder X’s menu, or download a copy here. A list of changes and download links, including localized versions, are available on the Default Folder X release page.
Version 2.4.8 of App Tamer is available. It now explicitly supports the new Music app in Catalina, meaning that if Music is playing something, App Tamer won’t slow or stop it even if it’s in the background.
This release also adds support for Google Chrome ‘Apps’, which you can create in Google Chrome by using the More Tools > Create Shortcut item in the “…” menu in a Chrome window. If you select “Open as window” when creating the shortcut, Chrome creates a separate application that relies on Chrome to render its window. That means that App Tamer needs to (and now will) keep Chrome running, rather than slowing or stopping it, when you’re using one of these separate Chrome apps.
And finally, version 2.4.8 of App Tamer also corrects several issues with its process control mechanism that could result in it not working correctly after your Mac wakes from sleep.
Version 1.0.5 of Go64 is out. If you’re not already aware of it, Go64 is our free app that scans your system for old apps containing 32-bit code that will no longer run correctly (or run at all) once you upgrade to macOS 10.15 Catalina.
This release fixes a bug that could cause the count of 32-bit and 64-bit applications to be incorrect, corrects a goof that could display (really) old PowerPC apps as 64-bit compatible, and scans TextMate .tmbundle files if you’ve got any installed.
If you already have Go64 on your Mac, just use its “Check for Updates” menu command. If not, head on over to the Go64 page to download your copy now!
The latest public beta of Default Folder X 5.4 is available, and offers improvements on both Catalina and older versions of macOS. Specifically, it adds support for the version of Path Finder distributed via SetApp, gives AppleScript developers access to applets and droplets in DFX’s Recent Files menu, and fixes a bug in Default Folder X’s handling of tabbed Finder windows.
Version 1.7.3 of Jettison is now available. It fixes a problem when running on Apple’s latest Catalina beta where it would try to eject Catalina’s new system data volume if the system was running from an external drive.
In addition, Jettison 1.7.3 also improves its error reporting and handling, allowing you to quit applications that are preventing a disk from being ejected. This release also addresses an occasional problem with disk images not getting completely cleaned up after being ejected.
More details and download links are available on the Jettison Release page. If you’re already running Jettison, just choose “Check for Updates…” from its menu in your menu bar to update to the new version.
Version 2.4.7 of App Tamer is out. The new release fixes a bug in its “Hide after X minutes” and “Quit after X minutes” features that could cause it to use unreasonable amounts of processor time when they were turned on for iTunes or Spotify. Not exactly what you want to happen in an app that’s designed to reduce the CPU usage on your Mac 🙂
Version 1.0.4 of Go64, our free app for determining which of your apps are macOS 10.15-compatible, is now available.
If you choose to list all the applications that Go64 has found, the new version will highlight all of the 32-bit apps in red. You can then sort the list by application name to see if you also have a 64-bit version of an app. If you do, then you don’t have to worry about finding an upgrade – just delete the 32-bit one shown in red.
Go64 1.0.4 also includes corrected website and company information for a number of applications, including those from Ashlar-Vellum, Avid, Slack, Steinberg and Valve.
You can get the latest version of Go64 here, or by choosing “Check for updates” in Go64 if you’ve already downloaded a previous version.
Go64 1.0.3 is available now – you can download it from the Go64 page. If you’re not already aware of it, Go64 is a free application that scans your Mac for 32-bit applications that will no longer work when you upgrade to macOS 10.15 Catalina.
The new version of Go64 will now show you Preference Panes that contain 32-bit code. It also properly skips apps that are built for non-macOS platforms even if they contain code to run on an Intel processor (this is for you, iOS developers).
Most importantly, however, version 1.0.3 provides a preference window where you can tell Go64 not to show apps that are located within specific folders.
In the image above, I’ve got an old copy of Microsoft Database Daemon selected – it’s part of Microsoft Office 2011, which I still have so I can test it with Default Folder X. I know it’s 32-bit but want to keep it around, yet I don’t want it shown in Go64’s search results.
To remove it from the results, I just drag the ‘Microsoft Office 2011’ folder shown in the path control (in the green square) to the ‘ignore list’ in the prefs window. That’ll remove it from the results quickly and easily, even though Office 2011 is still on my Mac.
This should make it easier to clean out your list of 32-bit only apps so you can focus on the ones you need to upgrade. Note that you can also drag a single app into the ‘ignore list’ if you just want to remove one app rather than all apps within a folder.
To prepare, I wrote Go64, a free application that scans your system for 32-bit apps and shows them all in one place, with version and website information to make it easier to assess whether you need to update or look for an alternative.
After Mojave started warning about 32-bit apps needing to be updated, Ronald Leroux, who does all the French localizations of my software, pointed out that there wasn’t really a good way to check for and update 32-bit apps on your system. The built-in System Information app does work, but it’s certainly not the most user-friendly, nor is it necessarily complete.
Over a weekend last fall, I put together a straightforward little app to scan for 32-bit applications and show them in a list. It took a fairly simplistic approach, and worked fine but was no more thorough than what System Information provides. Still, it was much easier to use, so I figured I’d release it in the Mac App Store. Then came the task of trying to get it approved: App Store Review rejected it because it asked for permission for the entire disk so it could scan for apps. That wasn’t something I could fix or work around. So I shelved it – there were higher priorities at St. Clair Software, plus dealing with the App Store always seems to ruin my day.
“It’ll only take a couple of days…” – famous last words uttered by nearly every software developer at some point in their careers.
As they say, the devil’s in the details, and dealing with the vagaries of what goes on inside applications got interesting. Go64 leverages Spotlight to compile a list of executables, but then does a deep dive into each 64-bit application to check for any helper apps, frameworks, services or plugins that might not be 64-bit. While I knew this could be an issue, Howard’s work highlighted just how common it is to have a mix of executables bundled within apps. Most of the time, it’s just for expediency, and developers do the proper juggling to run the correct one, but how’s a user to know? So Go64 does a bunch of checks to look for common methods, and if it still can’t make sense of things, errs on the safe side and flags the app with a little caution icon.
Clicking on “More Info” gives you the whole scoop:
This, of course, led to more complexity. As a developer, I don’t want to be bugged by hoards of people asking whether my app is Catalina-compatible just because some stupid “Go64” app noticed I include a 32-bit helper to deal with ancient Quicktime videos. So Go64 updates its internal “Ignore this warning” list periodically from the St. Clair Software website – that way it can inform users that even though the app contains 32-bit code, it’s compatible.
So developers, if your app contains 32-bit code but is Catalina-compatible, contact me with the bundle ID and version number of the app and I’ll add it to the list so Go64 gives users this message instead:
And to everyone else, I hope Go64 turns out to be useful for you. I certainly had a lot more 32-bit apps sitting on my Mac than I thought!