Why not just drag and drop the field tool from the status area onto your layout and right click it to select a script trigger?
That process would seem to be nearly identical to what you are describing here.
If you want to use your approach, you can double click the field to pop up the specify field dialog (or Field/Control | Setup... dialog in FM 10) so eventhat doesn't seem too difficult a way to go.
Didnt know that Mac had a Right Click :)
There's still control click to get the same result if your mouse has only one button.
The point being is I dont want to have to set the script trggers for all the fields I want them preset when they are identical to the copied field.
I can set the record::field itself easy enough with a double click but setting 3 script triggers per field seems a bit redundant.
If I want to change the script triggers then yes that would be an option.
Setting the same three script triggers (or any three script triggers) seems pretty extreme for a filemaker layout. What are you trying to accomplish with such a large number of script triggers on every field?
Some of its validation
Some of its manipulating environment variables
Its a variety of things
One of the more important ones is for contextual responses to things where I cant rely on the get functions about current etc.
I have some esoteric uses for the scripts. no matter what layout the field ends up on I want it to behave the same.
Its basically to ensure consistency across the environment for the most part.
It's sometimes a bit clunky, but validation can be performed at the data layer by setting validation rules on the field. This has the added benefit of being consistent across all layouts where you'd add this field.
Another labor saving trick that also enforces consistency in design is to set up your field the way you want it on one field and simply copy and paste it (or an entire group of items on one layout after another.) You can do this without setting up a specialized layout for the purpose like you've described in your first post.
I appreciate your response and Ive been doing that for a number of things but Im finding that I want a number of things set for a field type independent of the table/layout it comes from
My solution is pretty much the same thing except that I don't have to remember where I put that particular setup the first time as the layout becomes basicly a defined object pallet.