Popovers are supported in Table view. For popovers to display properly in Table view they should be placed in the Header or Footer part of the Table view layout.Popovers should not be nested. In other words, it is not recommended to put a popover inside another popover.You can script a popover to open or close. To open a popover using a script, use either the "Go To Object" or "Go To Field" script step to enter an object within the popover. To close a popover, use the "Close Popover" script step to close the currently open popover.
SavvyData's insight: Objects at the edge of a touchscreen are harder to hit and thus should be larger, reshaped or relocated. This is a proof case for "real" UX — where observing the user under actual conditions (or going back to the empirical, non-summarized, research) produces useful new insights.
Via SavvyData, Didier Daglinckx
This plugin for FileMaker Pro works with any connected camera. You can use your built in iSight camera, a USB connected WebCam or a FireWire connected device. You can use the plugin to show you a display of what the camera sees and then you can capture the current frame and store it as a image in many popular formats, or as an image onto your system clipboard.
Via David Anders
You can easily add a developer's information panel to your solutions by taking advantage of FileMaker Pro 13's new 'Hide Object' feature. Your panel can be set up to give you, the developer, many different bits of information that you don't need or want your users to see.
I was recently asked by a client about how to set up a record locking system. The idea of record locking is that when some event happens a record becomes no longer editable, preserving the contents...
1) Lock the entire record from deletion and editing by employing a customized privilege set and a field for tagging the records to lock. Related table records can be locked as well.
Pro: Simple, few moving parts.Con: Less flexible
2) Rather than locking an entire record, instead lock specific fields while still allowing some fields to still be edited. The lock field and privilege set are still employed, but in addition each field you wish to protect has a validation calculation attached to it.
Pro: More flexibleCon: More field definitions to modify.
Create your own custom FileMaker Pro plug-ins without re-inventing the wheel!
Minimum requirements of the current version:
Mac OS X: Intel Mac, 2048 MB RAM, Mac OS X 10.6 Snow Leopard, XCode 4.0, FileMaker Pro 10Windows: 500 MHz processor, 512 MB RAM, Windows XP SP3, Microsoft Visual Studio 2003, FileMaker Pro 10
Via David Anders
Water Quality Inspections Using iPads, FileMaker 12, and GoZync FullCity Consulting built this solution for a private company tasked with managing water quality in open bodies of water across large parts of two states.
FullCity Consulting built this solution for a private company tasked with managing water quality in open bodies of water across large parts of two states.
FullCity created their own FileMaker Go files, then used GoZync to sync inspections made offline with their client’s main FileMaker 12 solution.
Previously they were managing their workflow (from onsite service reports to state required reporting) on paper and using Access running under Parallels on a single Mac in the owner’s office. FullCity’s Adam Aronson recalls:
“When I first visited them there was a stack of service reports on the owner’s desk (2″ high!) that represented 60 days of invoices that had yet to be sent out.
I referred to this as ‘self imposed Net-90′.
Additionally, the information represented on the service reports needed to be aggregated yearly into a specific format for state reporting requirements.
Collecting all of the data and reentering it into Access (for printing the reports) was taking the two owners a ridiculous amount of time.”
I've been playing with an "exploration file" that helps Novice developers better understand how to work with file paths, containers and the many script steps that can use a $Path variable to access or create a different file at a different location each time that the script is performed.
I created a .fp7 version for FileMaker 11 and earlier users. Then I converted it to .fmp12 format and added a bit more to it for exploring the external storage and "interactive optimization" data format features newly added with FileMaker 12.
The download link downloads a zip file containing both versions of this file. You can download and then extract the file from the zip archive to use it.
The file is fully unlocked, you can easily examine the scripts in the file to find examples of how a $Path variable may be used and there are a number of calculation fields that can extract file names and file and/or folder paths from a container field after a file has been inserted into it.
You can also use this file to capture a valid file path to an existing file or folder on your computer for use in your own set variable script step for setting up your $Path variable. You can insert a file into a container field in the file and then copy and paste from one of the special calculation fields provided for that purpose. Syntax examples for combining the file path to such a folder with either a literal file name or one calculated from fields in your database have also been provided.
A special thanks to Jim Gurley for reviewing the file on a Mac system and for offering a number of helpful suggestions for improving this file.