Advanced Search
Search Results
1013 total results found
Modules
Modules are used to group a set of interfaces which usually belong logically together. It is possible to add, remove and reorder them using the corresponding buttons at the top of the module list. Properties In general, these offer a few basic options. H...
Interfaces
Interfaces define the inputs and outputs of the CGI Application. Depending on the module type either one or both types of interfaces are available. By selecting the corresponding tab, interfaces can be added, removed or rearranged using the buttons at the to...
XML Definition
Complex Types are defined in an XML Schema file which is located at “cgi_studio_connector/schema/ComplexType.xsd”. This file can be used to validate xml files and with some editors (e.g. Visual-Studio) and provide code-completion when writing the XML file. Co...
Converter
For conversion between the basic type and actual complex type, conversion functions needs to be available. This function must be implemented inside the “ComplexType” namespace (additionally to the default namespace for the Interface) and within the “ComplexTyp...
XML Definition
Native Functions are defined in an XML Schema file which is located at “cgi_studio_connector/schema/NativeFunction.xsd”. This file can be used to validate xml files and with some editors (e.g. Visual-Studio) and provide code-completion when writing the XML fil...
Implementation
The actual native functions must be implemented as part of the Action-Context class which will then be passed to the Interface to trigger them. The implementation must match the name of the specified function in the XML as well as the names, types and order o...
CGI Panel Overview
The CGI Panel (Player) is an application which provides insides into a generic CGI Studio application driven by the courier messaging framework. It also provides samples of several features. These features are core components like showing or hiding views or tr...
Associated Vertex Buffer
Here, the original mesh vertex buffer and wireframe vertex buffer information are managed as unique vertex buffer association information. Vertex Buffer Vertex buffer to provide model geometry data Wireframe Vertex Buffer Wireframe vertex buffe...
Demonstration
Demo Mode Action Action to start or end the demo mode. Common Properties Property Name Type Description Activate bool Activates or deactivates a demo mode DemoModeExecutor CgiStudioControl::DemoModeBehavior* Target demo mode be...
Editor
An editor for the Native-Function definition can be found here:“cgi_studio_connector/bin/ComplexTypeEditor.exe” If called with a file as first argument the editor will try to open the specified file. Complex-Types On the left side, Complex-Types can be a...
Editor
An editor for the Native-Function definition can be found here:“cgi_studio_connector/bin/NativeFunctionEditor.exe” If called with a file as first argument the editor will try to open the specified file. Native-Functions On the left side, Native-Functions ...
XML Definition
Builds are defined in an XML Schema file which is located at “cgi_studio_connector/schema/BuildProject.xsd”. This file can be used to validate xml files and with some editors (e.g. Visual-Studio) and provide code-completion when writing the XML file. BuildPro...
Sample
Below a sample XML file can be seen <?xml version="1.0"?> <BuildProject xsi:noNamespaceSchemaLocation="../../tools/ConnectorApp/Build/Schema/BuildProject.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ...
Editor
An editor for the Build-Projects definition can be found here:“cgi_studio_connector/bin/BuildProjectEditor.exe” If called with a file as first argument the editor will try to open the specified file. Global On this tab, global settings can be configured. ...
Interface-Buffer
The main class of the generated interface is called “Interface-Buffer”. This class is responsible to handle the data, actions and events from both sides and provide them to the other side. The Interface-Buffer class contains the following methods: Init Init...
Action-Context
The action context is used whenever any actions (except scene related actions) are executed. Besides some basic methods it must also implement all native-functions that the user wants to call via the interface. Required Methods There are some required method...
Scene-Context
The Scene-Context is used whenever scene related actions are executed. Here the user can provide his own implementation on how these actions are to be performed. Besides the Scene-Context itself there are also secondary classes (e.g. Scene/SceneTable) what the...
Data-Model
The basic Data-Model used by the Interface-Buffer is completely generated. However, the user can still override the handling of update requests if needed.