I fear that the problem is bigger than just R3MATPRPA_InputTypes, I admit that I have not explicitly tested all of these, but I think that none of the attributes that are of array type works properly in JS. Here are some examples:
* r3prim.GetPointsSelection() (R3PRIMA_PointsSelection) * r3prim.GetPoints() (R3PRIMA_Points) * r3subdiv.GetPoints() (R3SUBDIVA_Points) * r3subdiv.GetWeights() (R3SUBDIVA_Weights) * r3subdiv.GetUVCoords() (R3SUBDIVA_UVCoords) Some array attributes are not available at all from JS, for example: * R3SUBDIVA_Faces * R3SUBDIVA_FaceSelection * R3SUBDIVA_EdgeSelection * R3SUBDIVA_VertexSelection * R3SUBDIVA_HiddenFaces * R3SUBDIVA_SmoothVertices * R3SUBDIVA_HiddenUVFaces In case of R3SUBDIVA_Faces, I assume that the fact that the "struct r3subdivface" is not defined in JS, at least not in v4.5, explains it, but I do think that something is up with the array conversion between the SDK and JS. Regards, Fredrik Bergholtz On 28/03/07, Vesa Meskanen <[EMAIL PROTECTED]> wrote:
Hi, > I'd assume they read this list :) Yes we do. The bug appears to be in the discussed R3MATPRPA_InputTypes attribute handling. It is unusual and the standard JS approach does not handle it properly. We plan to fix this in future versions. Kind regards, Vesa
