As Apple continues to refine macOS 13 Ventura before its official release, I’m getting all of St. Clair Software’s apps up to speed on it. While both App Tamer and HistoryHound worked on the latest public beta versions of Ventura, there were a number of details that needed to be addressed.
Version 2.7.4 of App Tamer understands Ventura’s new security restrictions for Login Items and will ask you to approve its helper application when necessary. This release also fixes a bug in App Tamer’s window handling, and corrects a problem with a checkbox not being enabled in the settings for slowing down an app.
Because someone’s going to ask, the now-correctly-enabled checkbox is the “Also slow this app when it’s in front” feature. Even if you’re familiar with App Tamer, you may not have seen this as it only shows up when you hold down the Option key. As its name implies, this checkbox will slow down an app even when it’s frontmost. That’s usually not something you want to do, as it can make the app harder to use, but there are situations where it does make sense.
HistoryHound 2.3.3 is also available now, adapting its prompts for Full Disk Access permission so they work smoothly on Ventura. This update also adds some features, including support for the Orion web browser and new filters that you can use to narrow down searches of your browser history.
Oh, and to be consistent with Ventura, any references to “Preferences” in both apps now refer to “Settings” when you’re running on Ventura, because that’s what they’re called in the new, modern Mac world. Full details and download links are available on the App Tamer release page and the HistoryHound release page. The updates are free if you’ve already got a license for the app in question.
Among other things, the second public beta of Default Folder X 5.7, otherwise known as version 5.7b2, adopts Ventura‘s use of the term “Settings” rather than “Preferences.” Seems like that wouldn’t be a big deal, right? It turns out that those terms occur more frequently than you’d think in various dialogs and error messages, and have to be substituted on the fly to match the version of macOS you’re running. So I spent a couple of days bringing all that into conformance, then testing and localizing, and now it DFX fits in properly on Ventura.
Version 5.7b2 also adds a couple more interesting things, like support for Thomas Tempelmann’s Find Any File application. When you’re in an Open or Save dialog, you can now search with Find Any File from Default Folder X’s utility menu.
Find Any File can be helpful because it performs an exhaustive search based on a file’s name, modification date, and other filesystem properties. While Spotlight indexes these same properties as well as the contents of documents, it won’t always find all files – Spotlight omits the contents of some folders, as well as files contained within application packages and other special locations.
Default Folder X 5.7b2 also fixes a problem with its Recent File and Recent Folder tracking on Microsoft OneDrive that could result in files or folders being listed twice when they’re updated on OneDrive.
If you’re already running an earlier beta of Default Folder X 5.7, just choose “Check for Update” from its menu in your menu bar. If you’re not, head over to the Default Folder X Testing page to download a copy!
There’s a new public beta release of Default Folder X available: version 5.7b1. It’s compatible with Apple’s latest pre-release version of macOS 13 Ventura, and includes some fixes to work more smoothly with the new System Settings app, which is Ventura’s replacement for System Preferences.
System Settings is still rough around the edges, so there are a few quirks in the flow of granting Default Folder X the various privacy permissions it needs. Most notably, you’ll need to authenticate for each separate permission you give it (Accessibility, Full Disk Access, and Screen Recording). This is because System Settings doesn’t reliably set the state of the Privacy & Security controls if it’s already running when an app requests to be added. As a result, Default Folder X has to quit System Settings before it asks for each permission, or the little switch next to its icon will do nothing to the underlying setting when you turn it on and off. That means that instead of supplying your admin password or Touch ID once and turning on all the necessary switches all in one go, you’ll see the System Settings window go away, then come back, asking for admin permissions each time. Hopefully, this bug in System Settings will be resolved before Ventura ships and I can remove this little dance.
Default Folder X 5.7b1 also fixes a minor bug when running under Ventura and on older versions of macOS. There were circumstances in which Default Folder X could mistake your home folder for your iCloud Drive folder, showing the wrong name in the path menu that appears above the file listing in Open and Save dialogs. That’s been fixed.
Release notes and download links are available on the Default Folder X Testing page, or if you’re running a previous beta of Default Folder X 5.7, just choose “Check for Update” from its menu in your menu bar.
Version 2.7.3 of App Tamer is now available, fixing a couple of problems.
First, my apologies to folks using versions of macOS older than Big Sur: Changes in the last App Tamer update tightened up the spacing of its menu bar icon to comply with modifications Apple made to Monterey and Big Sur. Unfortunately, it also did that on pre-Big Sur systems, often making its icon too close to adjacent ones in the menu bar. I’ve fixed that in 2.7.3.
Second, internal changes that Apple made in macOS resulted in App Tamer reporting the CPU usage of one particular process – kernel_task – incorrectly. App Tamer would show either zero or astronomical values for kernel_task’s processor use, neither of which was correct. In App Tamer’s defense, the system’s approved public API was supplying those numbers and it dutifully reported them without prejudice. Some hunting around in the macOS source code (thank you Apple for making darwin Open Source!) revealed an alternate method that correctly reports the CPU usage of all processes, including kernel_task. So that fix is now available in App Tamer, making it a reliable source of CPU information for all processes again.
As usual, release notes and download links are on the App Tamer release page, or if you’re already using App Tamer, just choose “Check for Update” from its menu. This update is free if you’ve already purchased an App Tamer 2.x license.
