Registering and Unregistering Applications

The Design Editor requires applications to register their characteristics and entry points so that they can be called in the appropriate situations. If the user attempts to edit a design for which the view type is not registered, no window will be opened.

Registration is not the same as licensing. The application which is registered with the Design Editor still might not be licensed for use.

Both application view types and view subtypes are registered using the same procedure, defined in this section. However, because the data and application triggers can only be registered at the root (or view type) level an error is generated if these procedures are supplied for a view subtype.

Only the functions listed under the categories given below are supported for public use. All other functions, regardless of their name or prefix, and undocumented aspects of the functions, are private and are subject to change at any time.

• deAddAppCapabilities
• deRegApp
• deRemoveAppCapabilities
• deUnRegApp
• deRegUserTriggers
• deInheritEnabling
• deInheritMenus
• deUnInheritMenus
• deRegProbeTrigger
• deUnRegProbeTrigger
• deoRequireToolbars
• deoOnEvent

Return to top