Run times do not have any design access. The whole point is to provide a finished product that doesn't require the user to mess around with your design.
yes, I know. Customers need a minimum of flexibility to design a report. Other languages can use i.e. list&label. In lexware you can free design your bill form. If I give the same runtime solution to three people, each of them use their own bill form. So I need a minimum flexibility, that the customer can set the position for i.e. the printed header, to not overwrite his preprinted form. No one of these customers is interested in learning filemaker. The only one they want is set some parameters to position some line.
In other languages (like magicsoftware xpa) I can define a variable to set i.e. left position of a field in cm from border. And the enduser can set the value of these variable. Thats what I need.
And you can't use a script to modify layout design "on the fly". You might specify several "preset" layout designs--either by creating several different versions of the layout or by placing several different copies of the field on your layout. In the latter case, you can use "hide object when" to keep all but one copy of the field invisible and enable the user to pick which copy is or is not visible.
But I will offer one more caution here:
FileMaker inc. has listed "runtimes" as a deprecated feature for several versions now. A number of developers, myself included, keep pointing out to them how useful runtimes can be for some segments of the industry, but that "deprecated" status would make me very reluctant to make major business decisions on the assumption that runtimes, as we now know them, will be part of FileMaker's future.