Migration Guide : A. Features Introduced in OpenROAD 4.1 : OpenROAD 4.1 New Features : CompositeField Enhancements
 
Share this page          
CompositeField Enhancements
The OpenROAD 4.0 application development environment allows a developer to group various types of visual fields into a single field known as a CompositeField. The purpose of a CompositeField is twofold:
It allows the various fields within a CompositeField to be treated as named attributes of a parent class, thus inheriting many of the benefits of object-oriented programming.
It allows the creation of portable visual grouping of form fields that maintains inter-field geometry regardless of deployment platform.
When a CompositeField is used to represent the attributes of an OpenROAD user class, a restriction comes into play: the CompositeField can contain only fields contained in the user class. One cannot place "foreign" EntryFields or ButtonFields in a CompositeField based on a user class and take advantage of both object-oriented and portability benefits of CompositeFields. This restriction was relaxed.