Development Guide
Table Of Contents
- Chapter 1 Setting up databases for FileMaker Go
- Chapter 2 Differences between FileMaker Go and FileMaker Pro
- Chapter 3 Designing databases for FileMaker Go
- Chapter 4 Protecting databases in FileMaker Go
Chapter 3 | Designing databases for FileMaker Go 18
Text styles
The following text styles are supported in iOS: bold, italic, underline, title case, uppercase,
lowercase, word underline (appears as underline), double underline.
iOS doesn’t support: highlight, strike through, condense, extend, small caps, superscript, subscript.
Considerations for data entry on a device
1 Only fields are supported in the tab order. You can set up Tab and Return, but not Enter, to go
to the next field.
1 You can’t insert values into a field from an index on the device, and you can’t Auto-complete
using existing values.
1 Paragraph alignment, line spacing, and indentation might not display correctly in container
fields. To prevent these appearance issues, use center alignment in container fields.
1 Auto-Correction will not work in text fields that have script triggers set up to catch keystrokes.
1 Editing a text field in FileMaker Go reverts all styles in that field to plain text.
1 You can edit about 64K of text at a time.
1 Asian languages: sideways text and Furigana aren’t supported. Input method editors (IMEs) will
not work in text fields that have script triggers set up to catch keystrokes.
Considerations for performance on a device
Container fields
For container fields with images in remote files, the server scales the images before sending them
to the device. For container fields with images in local files, the device handles the images; for
improved performance use smaller images.
Layouts
Make several layouts with a minimum of objects instead of one layout with many objects.
For information about designing layouts, see “Tips for designing layouts and fields” on page 16.
Script triggers
To improve performance, use uncomplicated scripts in script triggers.