aboutsummaryrefslogtreecommitdiff
path: root/PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html
diff options
context:
space:
mode:
authorSheikh Dawood Abdul Ajees <[email protected]>2018-12-02 13:31:57 -0600
committerSheikh Dawood Abdul Ajees <[email protected]>2018-12-02 13:31:57 -0600
commit326e24039dd3f063afd211fad770e15bdd5ff4ea (patch)
tree94c7bcc15191736f263739c107d0a253b1629b0a /PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html
parentPhysX 3.4, APEX 1.4 patch release @25256367 (diff)
downloadphysx-3.4-326e24039dd3f063afd211fad770e15bdd5ff4ea.tar.xz
physx-3.4-326e24039dd3f063afd211fad770e15bdd5ff4ea.zip
PhysX 3.4, APEX 1.4 patch release @25354359v3.4.2-bsd
Diffstat (limited to 'PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html')
-rw-r--r--PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html b/PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html
index 2ecdfa05..d8372ea5 100644
--- a/PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html
+++ b/PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html
@@ -68,7 +68,7 @@
<p>Serialization and deserialization of a custom class can be achieved with the following steps:</p>
<ol class="arabic simple">
<li>Define a <em>PxConcreteType</em> and type info for the custom class. Make sure its type value is unique.</li>
-<li>The custom class needs to inherit from <em>PxBase</em> and implement it's interface.</li>
+<li>The custom class needs to inherit from <em>PxBase</em> and implement its interface.</li>
<li>Instance PxSerializerDefaultAdapter&lt;T&gt; and implement specialized methods where necessary.</li>
<li>If retargeting to other platforms is needed, implement <em>getBinaryMetaData()</em>.</li>
<li>Register the adapter and metadata, see <em>PX_NEW_SERIALIZER_ADAPTER</em> , <em>PxSerializationRegistry::registerSerializer</em> and <em>PxSerializationRegistry::registerBinaryMetaDataCallback</em>. Note that serializers also need to be unregistered before <em>PxSerializationRegistry::release</em> is called. The application is responsible for custom type serializer allocation and deallocation.</li>