DG Kernel Documentation


Skip Navigation Links.
Start page
Quick Start
Search Page
Installation
Overview of the software
What is new
Licensing
Collapse ModelsModels
Collapse DG Kernel ComponentsDG Kernel Components
Collapse API ReferenceAPI Reference
Interface List
Vector Space
Collapse General GeometryGeneral Geometry
Collapse ModelModel
Collapse ViewView
Collapse General ComputingGeneral Computing
Collapse Samples and TutorialsSamples and Tutorials
Collapse GraphicsGraphics
Collapse Math ObjectsMath Objects
Collapse DeprecatedDeprecated
Redistribution
Model Viewer
Open Source
Support
Skip Navigation Links Search Documentation


OCCT Bridge C++ Sample

 See also:  Technologies, Ogre Bridge Sample

Source code for the sample is provided as part of third-party source download: http://dynoinsight.com/Prod/V5_2/KC_5_2_ThirdPartySrc.zip

The solution file is located in DG Kernel\KC\Samples\VC\Technology\OcctBridge\. (Not in KernelCAD_5_2\Samples\VC\)

The main implementation is located in OcctBridgeView::DoTest() method called when the "Execute Test" button on the dialog bar is clicked.

The "Test Type" radio buttons determine the way ITechnology_DG interface is acquired. "Use COM" option simulates the case when a DG Kernel window is not available (possibly in case of a command line application or a component).

The OcctBridgeView::DoTest() tests various options described in ITechnology_DG topic.

It is recommended to inspect the other side of the communication implemented in OcctDgBridge class. The implementation is located in DG Kernel\ThirdParty\OCCT\src\TDocStd\OcctDgBridge.cxx, which is part of  ApplicationFramework\TKLCAF project of the DG Kernel\ThirdParty\OCCT\adm\msvc\vc12\OCCT.sln solution.

Step through the DoTest() code with debugger to see the calls executed.

Notice that if modification of OCCT code is required, only Release configuration will work with the sample as Debug version of DG Kernel component is not provided. Please use runtime methods: Tracing, pop-up messages, log files and the ITechnology_DG callback to debug the modification, which is normally small

Notice the call-back executed in OcctBridgeView::ExecuteDg(). It ends up in the OcctBridgeView::OnCallBack() method.