Replied 4 August 2017, 2:37 pm EST
in the attachment you will find a sample which describes my problem. When you move the controls in the frame you can see the behaviour.
" As for needing to highlight the frame control before placing controls inside it, this is a usability issue that exists in previous builds (in at least 1253) due to customers requesting a change in useability"
Sorry, but I don't really understand this sentence. What should be the final behaviour: having to select a frame and then adding a control to it or having ActiveReports automatically select the frame upon the first click when placing the new control? (Until build 1253 you could add controls to a non-highlighted frame.) Most of your customers desire the latter behaviour. The first behaviour is very inconvenient when you want to add 10+ controls to a frame control because you repeatedly have to highlight the frame control before you can put a control on it. So there's always one more step to add a control to a frame.
In the Thread "Frame controls problems in the designer" you wrote that most designs could be created without frames. But if you are using datafields which CanGrow and you are using lines to group some datafields, it is necessary to use frames, because the borders of the frame are growing with the datafields. Otherwise you would have to script it. But this is not reasonable for our customers.
If the designer behaviour has really changed in this respect, we would very much prefer a property to control its behaviour.
Thorsten Blawatt 2005/06/AR Frame Sample.zip