Note that the order of operations is important. With the code fragment above applied to a new document, a logical form is created automatically, inserted into the forms hierarchy, and the control model is inserted into this form. Moreover, if the hierarchy does not exist or is incomplete, for example, if the draw page does not have a forms collection, or this collection does not contain a form, this is also corrected automatically. If it is not, it is automatically inserted. In every document, when a new control shape is inserted into the document, through the API or an interaction with a document's view, the control model is checked if it is a member of the model hierarchy. We have previously said that every control model must be part of this hierarchy to prevent corrupted documents, but it is not harmful. The above does not mention inserting the control model into the form component hierarchy, which is a contradiction of our previous discussion. insert the shape into the shapes collection of a draw page.

announce the control model to the shape.

Looking at the example above, the basic procedure is: Int nYPos, int nWidth, int nHeight ) throws java. */ public static XPropertySet createControlAndShape ( String sFormComponentService, int nXPos, The height of the newly inserted property access to the control's model The ordinate of the position of the newly inserted nWidth The abscissa of the position of the newly inserted nXPos The service name of the form component to create, e.g. This will result in every view to this document creating a control described by the sFormComponentService

It creates a control shape, together with a control model, and inserts them into the document model. Note that control here is an incorrect terminology.

Apache openoffice org templates