Skip to main content


Showing posts from 2015

Capturing double-tap in FileMaker Go: Difficult but not impossible

N.B. The info in this article applies only to FileMaker 13 and 14. The problems that I complain of here may disappear, indeed, I hope they will disappear, in a future maintenance update to FileMaker 14. This info is good as of 5-20-15, but if you're reading this months later, check to see if the problems haven't since been fixed.

Written a database solution in FileMaker 13 or 14 that you are deploying on iOS devices, and want to distinguish double-taps from single-taps? For example, would you like a single tap on a record in list view simply to select the record, while a double-tap selects the record and views it in form view? Me, too.

So the way you're supposed to be able to do this is pretty straightforward (although it involves a little arithmetic). FileMaker Pro provides the basic tools in a layout script trigger OnGestureTap and a function Get(TriggerGestureInfo). In layout mode, you enable the OnGestureTap script trigger for the layout, and configure it to trigger a …

More about why I like the new navigation part in FileMaker Pro 14

I myself didn't completely "get" the navigation layout part at first. In this post I want to clarify a few things about the benefits of this new feature.

The new navigation layout part in FileMaker Pro 14 and FileMaker Pro 14 Advanced differs in two significant ways from the header/footer parts we've had since forever (and which we still have in 14):

Navigation parts don't zoomNavigation parts don't scroll out of sight
Well, it's a little messier than that, in reality. Let me elaborate on the messiness of it first, since the messiness may have some impact on why navigation parts took me a day or two to "get".

First potential confusion: objects in navigation parts don't zoom, but they are not completely inflexible. If you grab the edge of the window and make the window wider (I'm not talking about zooming the content, I'm talking about actually enlarging the window) then any objects in a navigation part that are anchored to both sides …

Correction of mistake in my review of FileMaker 14

There is a significant mistake in my Macworld review of FileMaker 14, published yesterday.

I spent a fair amount of time getting to know the new navigation layout part and in the process, coming to like it quite a bit. As I said in the review, at first glance, it looks like a duplicate of the header or footer layout part, but it's not. At the end of the relevant paragraph, I wrote this little summary:
I expect that FileMaker 14 developers will soon start using the navigation part for UI widgets like buttons, and will leave headers and footers for printed reports. I thought hard about the new navigation part; but I didn't give quite enough thought to how the old layout parts will and will not be affected by the new one.

The truth is, you will still want to put column field labels (on a list view layout) in a header part, so that they zoom with the body part. (This would apply to footers as well if you put any objects down there that need to stay aligned with the fields in the b…

Chrome becomes my default browser

Just discovered quite by accident that I can now zoom text in Chrome on the Mac (version 42) by double-tapping with two fingers. I gather this may have been added a little earlier this year but I only just noticed it. Anyway, that eliminates the last reason to keep using Safari, for me, anyway.

The other major advantage of Chrome is what Chrome calls "presentation mode". This provides true full-screen browsing, that is, the ability to fill the display with the contents of a single tab without menus, the bookmark bar, the location bar or visible tabs. Safari (version 8.0.5) can't do it at all. Opera Beta can do it, but does it badly. In Opera, once you hide the location bar, you can't type Cmd-L to enter a new URL. Presentation mode doesn't mean a lot to me on my iMac's big display, but on my 11" Macbook Air, getting rid of everything but the content area really makes a difference.

I'm getting closer to my dream: a world where all my hardware comes fr…

NEVER EVER leave the default Admin account enabled in FileMaker

I hesitate even to bring this up, because this is Dangerous Knowledge.

When you create a new FileMaker database, FileMaker gives you a default login account, with a default name and password. I wish it didn't and in my opinion, it shouldn't. But it does.

So here's what you need to know: Never, ever leave that default account enabled.

When would this matter?

If the database is stored on your computer and never shared with anybody, keeping the default account enabled means anybody who can get into your computer, can open the database — as developer. Now, this isn't really as big a deal as you might think, because they could do this even if you didn't use the FileMaker default login account. (Hint: Password crackers.) That's one more reason why you need to be careful about the security of your computer.

But God forbid the database is hosted on a server that is configured for remote access! In that case, physical access to the server is irrelevant. Any Internet tro…