When you place parts in the Composition Editor:
It is not good interface design for one part to overlay another part. Completely or partially overlaying a part can result in focus problems, causing users to see but be unable to select the part.
Parts included in the Composers category can contain any other visual parts that are placed on top of them. The parts contained by the Composers part become composites of the Composers part. For example, if you place an entry field, a list box, and two push buttons in a frame window, the frame window contains these parts and they in turn become the frame window's embedded parts.
The following table lists each of the palette
categories and specifies how you can use the parts in
each category.
Table 1. Categories and How You
Can Use Their Parts
| Category | Use Parts to Contain Other Parts? | Use Parts as Subparts? |
|---|---|---|
| Buttons | No | Yes |
| Data entry | No | Yes |
| Lists | No | Yes |
| Frame Extensions | No | No |
| Sliders | No | Yes |
| Composers | Yes | Yes |
| Models | No | No |
| Other | No | No |
For example, you can create a composite part that consists of a panel on which you have placed buttons and check boxes, each connected to a variable. When you embed this part in your main program, such as in a frame window, you place it and work with it as one part--not as a panel and separate buttons and check boxes.
Although the connections and variables for an embedded composite part are not displayed when that part is embedded, they are there. You do not see them because you do not edit them or their embedded parts directly within the main composite part. Using embedded composite parts reduces the number of connections and simplifies your work space.
To change the connections, the default text on the buttons and check boxes, or to otherwise alter this part, you must edit the part indirectly, as described in Editing Parts within a Composite Part.
Dropping Parts in the
Composition Editor
Property Sheets
Promote Features Window
