I started using this fork of Quaqua in a couple apps earlier this year, and specifically the FileChooser jar and libs. There generally has been no problem. However, one user recently reported that the filechooser was acting very badly on his OS X 10.10 computer. Specifically, whenever he clicked in the chooser's file listing there would be a very long pause, and then error dialog would pop up saying "There was a problem connecting to the server ’10.10.1.11’" (see attached image). Navigating to the specific directory where the file he wanted was located was extremely painful.

Building my app without Quaqua so that the filechooser is just the standard chooset, the user had no difficulty at all.

So my question is whether anyone else has ever encountered this particular problem? If so, any idea what was causing it and were you able to fix or work around it?

Are there plans for fixing the compatibility with Java 9 for class QuaquaTextFieldFocusHandler?

Current versions of macOS now produce this worrying warning.

objc[34377]: Class SheetSupport is implemented in both /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInterface (0x7fffa0d13080) and /Users/daniel/Documents/nuix/run-config-automation/dependencies/quaqua/libquaqua64.dylib (0x12564e258). One of the two will be used. Which one is undefined.

Presumably this means that Quaqua sheets have a 50% chance of not working? We're not using the sheet feature in the application we're actively developing, so it isn't a critical issue for us, but it might bite someone at some point, so I thought I'd raise it.

I've long been using Quaqua solely for the more Mac-like file chooser appearance and started using this fork earlier this year.

One of my app users just pointed out that when saving a file, the chooser no longer displays the filename suggested using the JFileChooser.setFileName(String) method but instead just displays "Untitled". This seems to be a problem specific to this fork of Quaqua, as I just checked the copy of Quaqua 9.1 I had archived and found that it does display the setFileName suggestion.

Seeing this on both Mavericks and Yosemite.