Open CASCADE Technology
6.5.4
|
#include <Standard.hxx>
#include <Standard_DefineHandle.hxx>
#include <Handle_XSControl_Controller.hxx>
#include <IFSelect_Profile.hxx>
#include <TCollection_AsciiString.hxx>
#include <Handle_IFSelect_WorkLibrary.hxx>
#include <Handle_Interface_Protocol.hxx>
#include <Handle_IFSelect_Signature.hxx>
#include <Handle_Transfer_ActorOfTransientProcess.hxx>
#include <Handle_Transfer_ActorOfFinderProcess.hxx>
#include <Handle_Dico_DictionaryOfTransient.hxx>
#include <TColStd_SequenceOfTransient.hxx>
#include <Handle_TColStd_HSequenceOfHAsciiString.hxx>
#include <TColStd_SequenceOfInteger.hxx>
#include <Handle_Interface_HArray1OfHAsciiString.hxx>
#include <MMgt_TShared.hxx>
#include <Standard_CString.hxx>
#include <Standard_Integer.hxx>
#include <Standard_Boolean.hxx>
#include <Handle_XSControl_WorkSession.hxx>
#include <Handle_Interface_InterfaceModel.hxx>
#include <Handle_Standard_Transient.hxx>
#include <IFSelect_ReturnStatus.hxx>
#include <Handle_Transfer_FinderProcess.hxx>
Data Structures | |
class | XSControl_Controller |
This class allows a general X-STEP engine to run generic functions on any interface norm, in the same way. It includes the transfer operations. I.e. it gathers the already available general modules, the engine has just to know it The important point is that a given X-STEP Controller is attached to a given couple made of an Interface Norm (such as IGES-5.1) and an application data model (CasCade Shapes for instance). A Controller brings a Profile, this allows to have several variants on the same basic definition, for instance keep the norm definition but give several transfer actors, etc Finally, Controller can be gathered in a general dictionary then retreived later by a general call (method Recorded) It does not manage the produced data, but the Actors make the link between the norm and the application More... |