"No Holding Back FileMaker Blogging"


Navigation:


Support this site by clicking on a sponsor below!



Beginner, Intermediate and Advanced Video Training


Recent Blogs:

Subsummary Sandwich
Subsummary Sandwich

Window Naming
Window Naming

The Front Door
The Front Door

Modular Scripting
Modular Scripting

FileMaker Videos
FileMaker Videos




FREE Beginner Video Training


Quick Tip:

Cascading Delete
Self-join or Same-Table relationships are very useful (two table occurrences from the source table related to each other), but be careful! Don't ever turn on the option to allow deletion of related records! If you do, whenever you delete a parent record you may delete more than you want. What happens is that since your related records are also your parent records, deleting records can cascade out of control. I have seen the deletion of a single record cause the deletion of all records in all tables.



Tips & Tricks Videos


Fun Stuff:

Jaymo
David Knight started calling me JoMo years ago and it kinda stuck. It's evolved from JMO to the current Jaymo but you can call me anything as long as you are friendly. Other nicknames include Hoss, n2 and Wiz.



RSS Feed
Window Naming
Level: Advanced
Category: Scripting
Tuesday, July 11, 2017
So, what's wrong with the default window name given by FileMaker? Imagine a user of your solution has multiple windows spawned on a small screen and goes to the Window menu to select the desired window. Without good window management, all he sees is "CONTACTS", "CONTACTS - 2", "CONTACTS - 3" and so on. With good window management, you can make it easy for users to quickly find the window they want without cycling through all of them.

Window Naming

In the last couple of years, I've adopted a technique for naming windows that's fairly dynamic. Rather than hard coding the window name from each script as needed, I prefer to use a combination of a single script, script trigger and a calculation field. I still name some windows via a specific script, such as a window containing a report since it doesn't change from record to record, but standard form and list view layouts are handled automatically by a script trigger.

The Calculation Field
Start by creating a calculation field that results in the text you want in the window title. The calculation result should change based on the record currently showing. I also like to include the table name. For example, a formula for a contact manager might be as follows:

"CONTACTS: " & name_first & name_last

Name the calculation field "window_title" to correspond with the terminology in FileMaker. Each table should have their own unique "window_title" field. For example, an invoicing solution might use:

"INVOICES: " & invoice_num

I usually copy and paste the field from table to table and make the corresponding text and field changes. It only takes a minute.

The Script
The script is only one line, using the Set Window Title step.

Set Window Title [Current Window; New Title: GetField(Get(LayoutTableName) & "::window_title")]

The calculation formula is entered in the Rename Window section of the Set Window Title dialog.

Window Naming

The GetField function requires a single parameter, specifying a table and field name in order to return the contents of that field. The table name needs to be supplied since script context requires it.

The Trigger
The OnRecordLoad trigger is ideal for this solution as it renames the window every time the record changes.

Window Naming


If you want the window name to update on new records as you fill out the fields, you'll also need to attach the script to every field referenced in the calculation using OnObjectExit. Otherwise, new record window titles will remain blank till they are navigated to again.

The only issue I have encountered is a conflict between OnRecordLoad and scripted finds. OnRecordLoad fires when transitioning from find to browse mode. This occurs after the Perform Find step, triggering the window naming script. This interrupts the find script, causing any errors that result from the find to be erased by the triggered script. The workaround is to test for not records found with Get(FoundCount) instead of Get(LastError).

Window Naming

My Approach
I like to design my first layout with this trigger already attached. Then, all I have to do is add the calculation field to any new table, duplicate the layout and make the necessary changes interface for the current table. This is a simple but effective technique for making sure all windows are named uniquely and cuts down on user frustration, mostly for power users who like to have multiple windows open at the same time.

Author:
John Mark Osborne
jmo@filemakerpros.com
www.databasepros.com

This blog is completely free. Please support it by clicking on one of the advertisers at the left side of the window. Thanks so much!

Add Comment:

First Name: *
Last Name:
Email: *
Web Site:
Comment: *
 Email Addresses will not be shared on the web site!