You save things into your Theme and can make changes to Default for each parts of your layout. It is also very important to save each part into your Theme to have a optimised solution. Have a look at my session from DevCon last year to learn more about what you should think about when you design in FileMaker
Thanks, but I fully understand themes and how to take advantage of them. The problem is that clicking on a border, no matter how slim, causes the entire contents of the field to be selected, which is an undesired feature in most cases.
Border or no border, padding or no padding, the user can accidentally select the contents. There must be a combination that does not allow for that to happen.
I think you are looking for a Product Idea, not a issue. Better you create a new Idea at
telling everyone how you think it should work. If FileMaker Inc like your idea and a lot of people like it to (vote it up) then there is a chance that it will be in one of the coming versions of FMP
Every field can be defined independly to select entire content on Field Entry, or NOT to select entire contents:
Use the Inspector, select desired field, select the Data tab in the Inspector, go down to Field Entry, unselect the option to Select entire contents on entry.
Now when you click in the field on a text word, cursor will locate there. However, clicking on the border of the field, seems to default to select entire field content.
Fields are NOT set to select entire field.
This is an issue of clicking on the padding or even the single pixel border for any enterable field.
Try it. Create a field with padding of 10, click on the padding. Now take away the padding, and you can still manage to click on the border and select all contents.
I'm trying to avoid script triggers, and even if you use Set Selection the users then lose the ability to set the cursor.
Yep, had not noticed that feature before, had never click on the border before, but always clicked on where the cursor was desired to be located.
Here's one way to control the behavior, with an OnObjectEnter script trigger.
Modified template file attached, with trigger script added to first name and last name fields.
The pause and refresh are not necessary but they let you observe the script in action.
It is understandable that you might like to able to control this without adding script triggers to all field objects.
Contacts.fmp12.zip 196.3 K
Thanks much Bruce. That's pretty much where we are right now (similar script) and will be passing this on to the client as an option.
I'm amazed that I have not observed the "select all" behavior in all the years of using FMP, or maybe I simply did not commit it to memory. It appears that a script trigger is the best answer since no amount of tinkering with the borders, padding, or themes has yielded better overall results.