Developer’s Guide
Table Of Contents
- Chapter 1 Getting started
- Chapter 2 Using FileMaker Developer features
- Chapter 3 Using the Developer Utilities
- Overview of preparing your solution files
- Modifying database solution files
- Considerations for a runtime database solution
- Binding databases into runtime database solutions
- Saving and reusing Developer Utilities settings
- Converting and upgrading solution files
- Removing full access privileges from databases
- Chapter 4 Distributing runtime database solutions
- Chapter 5 Customizing database solutions
- Chapter 6 Creating custom layout themes
- Chapter 7 Developing third-party FileMaker plug-ins
- About external functions
- About the example plug-in
- Installing, enabling, and configuring the example plug-in
- Description of the FMExample plug-in’s external functions
- Using the example plug-in
- Customizing the plug-in example
- Requirements for writing external function plug-ins
- FileMaker messages sent to the plug-in
- Avoiding potential Mac OS X resource conflicts
- Providing documentation for your plug-in
- Registering your plug-in
- Appendix A Feature comparison of the runtime application with FileMaker Pro
- Index
Creating custom layout themes 55
Specifying default values for themes
FileMaker Pro and FileMaker Developer use default values to
replace attributes that are invalid or missing. For each theme listed in
a theme file, you can specify whether the default values are
determined by the current layout settings, which change when a user
changes them, or by standard layout values, which are the same
values that FileMaker uses when creating a file for the first time.
<THEMEDEFAULT VALUE=”CURRENT”/>
<THEMEDEFAULT VALUE=”STANDARD”/>
If you don’t specify a value for the THEMEDEFAULT element in
the theme, FileMaker Developer will use standard layout values by
default.
Using values for patterns and colors
The values for the patterns in the FileMaker Pro and FileMaker
Developer pattern palette are numbered consecutively, starting with
the top row and counting from left to right, where the value for the
pattern in the top left corner is 1. Five patterns in the first row can
also be defined with words: NONE (= 1), SOLID (= 2), DKGRAY
(= 6), GRAY (= 7), and LTGRAY (= 8).
Note The first pattern (value = 1) is transparent and the second
pattern (value = 2) is solid. For objects with a color fill, be sure to use
the solid pattern.
STYLE Character styles for text in fields,
text blocks, and field labels. More
than one style can be specified,
separated by commas or spaces.
No error checking is done for
contradicting styles, such as
UPPERCASE and LOWERCASE.
The PLAIN style value overrides all
other style values.
STRIKEOUT and STRIKETHRU
values are the same.
STYLE = “PLAIN”
STYLE = “BOLD”
STYLE = “ITALIC”
STYLE =
“STRIKEOUT”
STYLE =
“STRIKETHRU”
STYLE =
“SMALLCAPS”
STYLE =
“UNDERLINE”
STYLE =
“WORDUNDERLINE”
STYLE =
“DBLUNDERLINE”
STYLE =
“UPPERCASE”
STYLE =
“LOWERCASE”
STYLE = “TITLECASE”
STYLE =
“SUPERSCRIPT”
STYLE = “SUBSCRIPT”
STYLE = “CONDENSE”
STYLE = “EXTEND”
STYLE = “ITALIC,
BOLD, SMALLCAPS”
This
attribute
Is used to describe these
characteristics
And may contain
these values