Difference between revisions of "GeometryCHUNK"
From BRL-CAD
Stpierre96 (talk | contribs) (→Description) |
Stpierre96 (talk | contribs) (→Description) |
||
Line 4: | Line 4: | ||
[[IBME_GeometryService#NetMsg_Class|NetMsg]] that contains a single serialized Geometry object. Extends [[GenericMultiByteMsg]] (thus contains those fields also). The String field from [[GenericMultiByteMsg]] is used as the Data field. | [[IBME_GeometryService#NetMsg_Class|NetMsg]] that contains a single serialized Geometry object. Extends [[GenericMultiByteMsg]] (thus contains those fields also). The String field from [[GenericMultiByteMsg]] is used as the Data field. | ||
− | If a [[GeometryREQFAIL]] message is displayed, this indicates that the GeometryCHUNK has failed. <BSRJ> | + | If a [[GeometryREQFAIL]] message is displayed, this indicates that the GeometryCHUNK object has failed. <BSRJ> |
==Byte Format== | ==Byte Format== | ||
No additional fields beyond that of the [[NetMsgTypes|Common Header]] and [[GenericMultiByteMsg]] | No additional fields beyond that of the [[NetMsgTypes|Common Header]] and [[GenericMultiByteMsg]] |
Revision as of 12:54, 30 December 2012
Description
NetMsg that contains a single serialized Geometry object. Extends GenericMultiByteMsg (thus contains those fields also). The String field from GenericMultiByteMsg is used as the Data field.
If a GeometryREQFAIL message is displayed, this indicates that the GeometryCHUNK object has failed. <BSRJ>
Byte Format
No additional fields beyond that of the Common Header and GenericMultiByteMsg