Use this tab page to configure the default class to use when:
The class preferences simply determine what classes are used when objects are created from the DDO Explorer or a new component wizard. When you create new sub-classes using either the New Class option or the Multi-class wizard option, you may wish to make these classes your preferred class for these operations.
Note that classes created via these two options never automatically update these preferences – it must be done here in this dialog.
Also note that once new objects are created via a new component wizard or a DDO explorer selection that you can easily change the source code and assign the object to a different class.
A list of classes that can be configured are displayed in a three column grid. For each default class listed in this grid (e.g., dbForm), a class preference must be identified by assigning a class name and a file name where that class is defined (e.g. cMyWSdbForm, cMyWSdbForm.pkg). By default, the class preferences listed are the standard system classes (e.g., dbForm, DFEntry.pkg). If you have created another class that you would sooner use, you may define that preference. These preference classes should almost always be a subclass of the default system class.
Some classes are "composite classes", which are two or more classes that are conceptually bound together in operations. For example, a tab page class and a tab dialog class. In addition to adding composite classes to the workspace preference list, you will also need to add a CompositeClass class meta-data tag to your class code.
This column lists each system class where the Studio supports subclasses in DDO Explorer operations, Create New Wizards or as a data dictionary subclass.
Use this column to specify the name of a subclass that the Studio will use when creating an object of the corresponding default class from DDO Explorer, one of the wizards in Create New, or for data dictionary classes.
The combo list contains the list of all classes listed in the current workspace's Class Palette.
Most preference classes should already be defined in your class palette and therefore should be in this list. If you select the class from this list, the correct workspace class file will be automatically selected.
If you are selecting a class that is not in the class palette, you might first want to check that you really want to do this. If you really want to use this class as a preference, it should probably be in the class palette. The exception to this rule will be the Data Dictionary class, which should not be defined in your class palette.
If the class is not in your class palette (most likely a Data Dictionary class), you will want to first select the workspace class file. This will add the class to this list, allowing you to make your selection.
Enter the filename of the package where the workspace class is declared. To browse for the desired file click the prompt button to activate the Select File dialog. You should rarely need to make this selection because selecting the workspace class name will select the class file for you. The exception to this will be, as noted above, the Data Dictionary class.
This specifies the class that is used for the command bar system object when choosing the Add Standard Menu/Toolbars context menu option in the Visual Designer.
This specifies the default class that is used in the Visual Designer when creating a new menu or toolbar item.
Configure Workspace Properties