InterfaceTypes - Supported interface types
Enumarators overview
- IFT_none
(-1) - Use no interface support
- IFT_odabaInterfaceAndSystemCPP
(3) - Support new and old ODABA C++ interfaces
- IFT_odabaInterfaceCPP
(1) - Support new ODABA C++ interfaces
- IFT_odabaOSI
(5) - Support ODABA Script interfaces
- IFT_odabaSystemCPP
(2) - Support old ODABA C++ interfaces
- IFT_undefined
(0) - Interface support not defined
Enumerator details
-
IFT_undefined - Interface support not defined
In this case interface support is done according to the interface type of the parent object or - if there is no parent object available - according to the option set for Options.Implementation.IF_ImplementationType.
Code: 0
to list -
IFT_odabaInterfaceCPP - Support new ODABA C++ interfaces
The resource database will be initialized with the new ODABA interfaces (ODABA namespace, GUIInterface namespace). Moreover class, module and project implementation are supported for these new ODABA interfaces.
Code: 1
to list -
IFT_odabaSystemCPP - Support old ODABA C++ interfaces
The resource database will be initialized with the oldODABA system interfaces (OPA Project classes and ODCP Project classes). Moreover class, module and project implementation are supported for these ODABA system interfaces.
Code: 2
to list -
IFT_odabaInterfaceAndSystemCPP - Support new and old ODABA C++ interfaces
The resource database will be initialized with both, the new ODABA interfaces (ODABA namespace, GUIInterface namespace) and the old ODABA system interfaces (OPA Project classes and ODCP Project classes).
For supporting class, module and project implementation for these objects either the new interface type (IFT_odabaInterfaceCPP) or the old system one (IFT_odabaSystemCPP) should be defined. If support (e.g. initializing a context class) is ambiguous, the new style is used.
Code: 3
to list