![]() |
PK_PART_transmit_o_t |
struct PK_PART_transmit_o_s { int o_t_version; --- version number PK_transmit_format_t transmit_format; --- (PK_transmit_format_neutral_c) PK_LOGICAL_t transmit_user_fields; --- (PK_LOGICAL_true) int transmit_version; --- (0) PK_LOGICAL_t transmit_nmnl_geometry; --- (PK_LOGICAL_false) PK_POINTER_t transmit_indexed_context; --- (NULL) PK_transmit_meshes_t transmit_meshes; --- (PK_transmit_meshes_separate_c) }; typedef struct PK_PART_transmit_o_s PK_PART_transmit_o_t; This option structure contains options pertinent to transmitting parts.
PK_DEBUG_transmit
PK_PART_transmit
PK_PART_transmit_b
PK_PART_transmit_u
Description of fields: 'transmit_format' Format of the XT data. Permitted values are PK_transmit_format_text_c PK_transmit_format_binary_c PK_transmit_format_typed_binary_c PK_transmit_format_neutral_c PK_transmit_format_indexio_c PK_transmit_format_applio_c 'transmit_user_fields' PK_LOGICAL_true if user fields are to be transmitted. 'transmit_version' By default (i.e. 'transmit_version' is zero), data saved using Parasolid 14.0 and later is backward compatible at least as far as the previous major version. All information associated with the part is stored in the saved XT data, including information that may not itself be recognised by the earlier version. E.g., data saved from 15.x would be backward compatible to at least v14.x, together with all the information they contain. By explicitly setting 'transmit_version' to a non-zero integer, an alternative method is used to achieve backward compatibility. Using this method, the data is saved using the precise format of the previous version. Any information associated with the part and not recognised by that previous version will not be present in the part data when it is saved. The integer specifies which version to use. For example, 101 would indicate Parasolid 10.1, and 90 would indicate Parasolid 9.0. The oldest version that can be used is 7.0 and the current version is allowed. For versions before 9.0, a part file can only contain a single part. 'transmit_nmnl_geometry' If PK_LOGICAL_true, then any nominal geometry on a part is saved, otherwise such geometry is stripped from the transmitted data. This field is ignored if 'transmit_version' is prior to V10.1: nominal geometry is unconditionally removed as earlier versions of Parasolid do not understand nominal geometry. 'transmit_indexed_context' Application specific storage when 'transmit_format' is PK_transmit_format_indexio_c. 'transmit_meshes' Where any mesh data in the parts are stored. If this option is PK_transmit_meshes_separate_c then all mesh data are transmitted to a separate file with the same 'key', which is opened with guise FFCXMM (transmit file containing mesh data). If this option is PK_transmit_meshes_embedded_c then all mesh data are stored within the part file instead, thus allowing data for each mesh to be individually received when needed using the receive option 'receive_using_seek' set to PK_receive_using_seek_yes_c. To support PK_transmit_meshes_embedded_c, 'transmit_format' must be one of the binary formats and the Frustrum seek function 'ffskxt' must be registered using PK_SESSION_register_fru_2. Part files with embedded mesh data can still be received without using seek. This option is ignored for PK_PART_transmit_b.Generated on: Fri, 04 Oct 2024 12:21:28 GMT