FileMaker Pro 7: Still doesn’t support command-click in window title bar

Posted by Pierre Igot in: Macintosh
November 23rd, 2004 • 1:14 am

You know how, in most Mac OS applications (including pre-Mac OS X applications!), you can command-click on the title of a document window and a pop-up menu appears with the path to the document you are currently viewing/editing, so that you can open the document’s containing folder with a single click, instead of having to burrow your way through folders and subfolders in the Finder to locate that folder manually?

Well, here’s FileMaker Pro 7, a mature Mac OS X application developed by a fully-owned Apple subsidiary. You’d think it would support such a fundamental feature, wouldn’t you?

Think again. When you have a FileMaker document open in FileMaker Pro 7, command-clicking on the document window’s title bar does… absolutely nothing. There is effectively no way of opening the folder that contains the FileMaker document in question in the Finder. You have to switch to the Finder first and then, as I said, burrow your way through folders and subfolders until you can locate the folder in question manually.

This is just shameful stuff. Unfortunately, it’s perfectly in line with other fundamental problems in FileMaker that have remained unaddressed either by FileMaker or by Apple over the years.

Shame on FileMaker. Shame on Apple.

2 Responses to “FileMaker Pro 7: Still doesn’t support command-click in window title bar”

  1. rwp says:

    I agree Pierre. FileMaker Pro is one of the worst-behaved large OS X apps. Why does its icon bounce like a baby having a tantrum in the Dock when I double click to open an FMP file, but then shift focus to another window? Just open in the background for cripes sake!
    Pitiful. The FMP user interface needs a major fix to become like real Mac apps. I don’t need more features until the basic behaviour is fixed.

  2. Pierre Igot says:

    Reported on the intrusive icon bounce here :). It is mightily irritating.

    It is really hard to fathom. While I can understand — up to a point — the focus on cross-platform compatibility, we are talking about basic Mac OS compliance here.

Leave a Reply

Comments are closed.