HOOPS Exchange Documentation

< Home

< Reference Manual

< File Formats

PROGRAMMING GUIDE

Contents

1.0 Introduction

2.0 Getting started

3.0 Product occurrence

4.0 Reading geometry

5.0 Entity attributes

6.0 Views and PMI

7.0 Advanced functions

4.3 Translating B-rep to Parasolid

If you are a Parasolid user, HOOPS Exchange 2015 and later includes a bridge to bring your data directly into an open Parasolid session. During the import process, the bridge uses native Parasolid APIs to ensure the highest quality model import. Additionally, the algorithm calls a set of healing functions to repair any incompatibilities that may arise. You are able to export either the entire model or individual representation items.

Two API methods implement this functionality:

Regardless of which way you export, you always use a A3DRWParamsExportParasolidData structure to supply the export options.

// ... set your desired export options here
int iNbPkParts;
PK_PART_t* pPkParts;
A3DAsmModelFileTranslateToPkParts(sHoopsExchangeLoader.m_psModelFile,
&sExportOptions, // export options structure
&iNbPkParts, // [out] length of pPkParts
&pPkParts); // [out] PK_PART_t entity IDs

For a complete working example, see the "TranslateToPkParts" code sample in the HOOPS Exchange package. To use this functionality, you must include hepb.dll when you distribute your application on Windows platforms.