|
Rambling continued ... another option would be to split the frame functionality into two seperate objects ... the FRAME object and the GROUPBOX object ... very .NET like in some respects (the .NET FRAME is called GROUPBOX) ...
The FRAME object would be used for visual effect only - it would be transparent and serve as a que that the controls contained (bad word) within its borders are related in some way ... but other in that, would NOT support the ability to host child objects. If you moved the FRAME, the other controls would not move with it. Mutually exclusive RADIOBUTTONS would need the TABGROUP property set in order to enable exclusivity (?!)
The GROUPBOX object would look similar to the FRAME object, but would have full support for control containment - controls can be created inside the GROUPBOX, and if the GROUPBOX moved - the controls would go with it. The GROUPBOX would be NON-TRANSPARENT - at least until I get it to support all possible scenarios - at which time we can make the FRAME object obsolete - which is what .NET has done.
| 
