HOOPSACIS Bridge Use Cases.docVIP

HOOPS/ACIS Bridge Use Cases From DocR22 HOOPS Jump to: navigation, search Contents [hide] 1 Initialization and Shutdown 2 Reading ACIS Files 3 Creating and Rendering ACIS Entities 3.1 Defining ACIS Geometry 3.2 Rendering ACIS Geometry 3.3 Inserting ACIS Geometry into the HOOPS database 3.4 Deleting ACIS and HOOPS Geometry 4 See Also Initialization and Shutdown To initialize the HOOPS/ACIS Bridge, call api_initialize_hoops_acis_bridge in an application initialization routine. This function initializes the ACIS components that the Bridge uses and registers HA_History_Callbacks with the global history callback list. All geometry rendered via HA_Render_Entity routines will be mapped to corresponding segments and geometry in the HOOPS graphics database. (HOOPS does not need an explicit initialization routine, as it is automatically initialized during the first call of a HOOPS function.) If your application performs advanced ACIS operations, then you may need to call api_initialize_* to start up the modules you are using. These calls should be made just after calling api_initialize_hoops_acis_bridge. Likewise, any modules that you initialize should be shut down just prior to calling api_terminate_hoops_acis_bridge. The ACIS modules initialized and shut down within the calls to api_initialize_hoops_acis_bridge and api_terminate_hoops_acis_bridge are: Booleans, Faceter, and Rendering. To terminate the HOOPS/ACIS Bridge, call api_terminate_hoops_acis_bridge. This should be called in an application-cleanup routine, when ACIS is no longer needed. This does not shut down the HOOPS Graphics System; HOOPS HC_Reset_System will still need to be called to directly shutdown HOOPS: void MySolidHoopsAppCleanup() { api_terminate_hoops_acis_bridge(); // shutdown ACIS api_stop_modeler(); // shutdown ACIS terminate_base(); // shutdown ACIS HC_Reset_System(); // shutdown HOOPS }