Hi Michalis,<br><br>Thanks for your clarification =)<br><br>Regards,<br>Alexander Dong Back Kim<br><br><div class="gmail_quote">On Mon, Sep 7, 2009 at 11:53 PM, Michalis Kamburelis <span dir="ltr"><<a href="mailto:michalis.kambi@gmail.com">michalis.kambi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Alexander Dong Back Kim wrote:<br>
> Dear members,<br>
><br>
> While I'm going through all the nodes, I've realized that none of the<br>
> nodes use "SFMatrix3d" as the member variable. Did I miss something? or<br>
> X3D specification just declares the field for future conveniences?<br>
><br>
<br>
</div>Grepping through source code of my engine (I have code to initialize<br>
nodes from all components from X3D 3.2) SFMatrix3d is indeed not used by<br>
any standard node. Same thing for e.g. SFMatrix4d and MFImage field types.<br>
<br>
It can be used by future nodes. It can also be used by existing<br>
EXTERNPROTOs (in case someone makes an extension using SFMatrix3d), and<br>
may be declared as a field type inside Script nodes.<br>
<font color="#888888"><br>
Michalis<br>
</font></blockquote></div><br>