Create an app object
Overview
Create an app object (for example a sheet, a story, ...) using the CreateObject method
Examples
Example 1:
1. Create the sheet SH01 (qId is SH01).
The client sends:
The engine returns:
The sheet SH01 is created. Since the sheet definition contains qChildListDef, a GetLayout on the sheet will display the children of the sheet.
The handle of the sheet is 2.
2. Create a list object in the sheet. The request has 2 as a handle (qHandle) because the sheet has 2 as a handle.
The client sends:
The engine returns:
The list object LB01 is created and its handle is 3.
3. Get the layout of the sheet (qhandle is 2).
The client sends:
The engine returns:
The list object is added to the list of children of the sheet (qChildList).
Example 2:
1. Create a story story01.
The client sends:
The engine returns:
The story is created. The handle is 2. Since the story definition contains qChildListDef, a GetLayout on the story will display the children of the story.
2. Create a slide slide01 (qId is slide01).
The client sends:
The engine returns:
The slide slide01 is created. Its handle is 3.
3. Create another slide slide02 (qId is slide02).
The client sends:
The engine returns:
The slide slide02 is created. Its handle is 4.
4. Get the layout of the story. The handle of the request is 2 because the handle of the story is 2.
The client sends:
The engine returns:
The story contains two children: slide01 and slide02.
Example 3:
1. Create the sheet SH01 (qId is SH01).
The client sends:
The engine returns:
The sheet SH01 is created and has 2 as a handle.
2. Create the sheet SH02 that is linked to the sheet SH01 (qExtendsId is SH01).
The client sends:
The engine returns:
The sheet SH02 is created. This sheet is linked to the sheet SH01 and has 3 as a handle.
3. Get the layout of the sheet SH02 (qHandle is 3).
The client sends:
The engine returns:
The sheet SH02 has the same properties as the sheet SH01.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!