c357e42610
Expose interface of OpenGl_View (OpenGL graphics rendering methods) to client code and collecting all high-level API methods of application views in V3d_View class. 1) Exposing interface of OpenGl_View: The OpenGl_View inherits from new class Graphic3d_CView. Graphic3d_CView is an interface class that declares abstract methods for managing displayed structures, display properties and a base layer code that implements computation and management of HLR (or more broadly speaking view-depended) structures. In new implementation it takes place of eliminated Visual3d_View. As before the instance of Graphic3d_CView is still completely managed by V3d_View classes. It can be accessed through V3d_View interface but normally this should not be required as all its methods are completely wrapped. In more details, a concrete specialization of Graphic3d_CView is created and returned by graphical driver on request. Right after creation the views is directly used for setting rendering properties and adding graphical structures to be displayed. The rendering of graphics is possible after mapping a window and activating the view. The direct setting of properties makes obsolete usage of intermediate structures with display parameter like Visual3d_ContextView and etc (the whole package of Visual3d become redundant). 2) Collecting all high-level API methods of application views in V3d package: The patch includes elimination of Visual3d layer. All of its methods that could be previously used by application are now exposed and should be accessed on the level of V3d entities. - Introduced new class Graphic3d_CView. This is a base class for render views. Made possible to specialize concrete instances of the class by graphical driver. - Moved all methods managing rendering views into interface of Graphic3d_CView. The corresponding methods were removed from interface of graphical driver. 3) Eliminated Visual3d package: - Logic of managing display of structures was put from Visual3d_ViewManager into Graphic3d_StructureManager. - Removed Visual3d_View class. Logic of managing computed structures was put into base layer of Graphi3d_CView. - Removed all intermediate structures for storing view parameters e.g. Visual3d_ContextView. All settings are kept by instances of Graphic3d_CView - Removed Visual3d_Light intermediate class. All light properties are still stored in Graphic3d_CLight structure. The structure is directly access by instance of V3d_Light classes. - Moved all needed enumerations into Graphic3d package. 4) Update package D3DHost to new changes. 5) Update code of OCCT samples to new changes.
OCCT CSharp sample
This sample demonstrates how to use OCCT libraries in .Net application written using CSharp and Windows Forms or Windows Presentation Foundation (WPF).
The connection between .Net and OCCT (C++) level is provided by proxy library OCCProxy, written in C++/CLI. The proxy library contains a single ref class encapsulating OCCT viewer and providing the functionality to manipulate this viewer and to import / export OCCT shapes from / to several supported CAD file formats (IGES, STEP, BREP).
The sample implements two approaches to the development of a user interface with C#. Both applications provide the same functionality as the standard OCCT Import/Export sample. The first project is called IE_WinForms and uses Windows Forms for GUI. The second application is called IE_WPF_WinForms and uses Windows Presentation Foundation.
Note a few important details:
-
OCCT template class NCollection_Haft is used to encapsulate C++ class into a field of ref class;
-
It is necessary to explicitly set the target platform for C# assemblies to x86 in project Properties - Build to work consistently on 64-bit systems with OCCT libraries built in 32-bit mode;
-
this sample demonstrates indirect method of wrapping C++ to C# using a manually created proxy library. There is an alternative method of wrapping individual OCCT classes to C# equivalents to make their full API available to a C# user and to let the code be programmed on C# level similarly to C++ one. See the description of OCCT C# Wrapper in Advanced Samples and Tools at http://www.opencascade.org/support/products/advsamples
-
in WPF sample, WinForms control is used to encapsulate OCC viewer since WPF does not provide the necessary interface to embed OpenGl view. Other possible solution could be to render OpenGl scene in an off-screen buffer and to map it to WPF control as an image. That approach would allow using all WPF features to control the OCCT viewer.
Run msvc.bat to start MS Visual Studio for building the sample. Note that project files are provided only for VS 2010, you can open them in newer versions of Visual Studio the using automatic converter.
After conversion check option Target framework in the properties of C# projects (tab Application) to make sure that it corresponds to the version set in the properties of C++ projects (e.g. .Net Framework 4.0 for VS 2010).
Run run_winforms.bat or run_wpf.bat to launch the corresponding sample.
Note that all batch scripts use the configuration defined in OCCT custom.bat file as default; you can provide arguments specifying VS version, bitness, and mode to override these settings, e.g.:
> msvc.bat vc10 win64 Debug