Default Folder X 4.2d10 available

Here’s another development build with refinements to Default Folder X’s new OpenMeta support:

Changes include:

  • Made the autocompletion always respect the case of what you’ve typed, rather than forcing the capital or lowercase form you used last time.
  • Fixed an OpenMeta problem that resulted in previous builds failing to start up under Mac OS 10.4.
  • Changed OpenMeta tag fields so that it no longer selects all of the tags when Default Folder X first displays them.
  • Fixed the localized nibs – they were not connecting the controls in the Spotlight comment window correctly.
  • A new AppleScript command, ClearRecentFolders, clears the list of recently used folders in the currently active folder set.
  • Corrected a bug that caused Default Folder X to print warning messages in the console like ” ** No alias data for item 0 (folder name) **” when there was a Smart Folder open in the Finder.
  • Streamlined DFFinderWindowServer to minimize overhead.

Please keep the comments and feedback coming!  As soon as I’ve got localization strings back, this version should be ready to roll.  In the meantime, I’ll work on compatibility with future operating system changes 😉

2 Responses to “Default Folder X 4.2d10 available”

  1. HerbertKornfeld says:

    Re: autocompletion respects the case of what’s typed

    I actually prefer the former behavior. I like for my tags to always be capitalized, and I like that I can create these tags without worrying about the capitalizations. Could you perhaps make this an option for users like me who prefer it the other way around? Or is there a simple tweak I could do to revert this behavior?

    Thanks in advance, and keep up the great work.

  2. Jon says:

    Well, you could just start typing tags with the capitalization you want 🙂 After all, for tags that aren’t in your tag history, you’ll have to do that anyway to get them into the history with the capitalization you want. If I change the behavior back and you forget to capitalize a new tag, then you’ll be stuck with those being completed without capitalization. I think forcing the capitalization based on the tag history is a bad idea because it removes too much flexibility.

    Now, adding a setting to auto-capitalize tags (regardless of the case you use when typing them) would be something to consider, at least…

Leave a Reply