Horde3D

Hi everybody!

I'm sorry but this is not a bug report, it's a feature request to add new functions to the core API (dind't know where to post...).
The "problem" I'm having is with the setNodeTransform() function, for example I want to set a node translation without changing the rotation and scale of the node (or set the node rotation without changing the node translation and scale). Right now it's not prossible, with the setNodeTransform() function I've to apply all three parameters at once. It would be cool to have functions like: setNodeTranslation(), setNodeRotation() and setNodeScale() for that matter.

If you think it's reasonable to add them, please do it as I see them as very handy functions.


Thank you very much for taking the time on reading this post,

Federico Omoto

That's something I've thought about some time ago, too. I remember that I discussed this with Nicolas, but I couldn't remember what was the final decision.
At my projects, I added a wrapper for scene graph nodes that adds additional functionality like translateRelative, translateAbsolute, etc. I guess Nicolas wanted to keep the interface to Horde3D simple and if you want to handle graphical objects, you normally have to add something like such a wrapper anyway.

I find it most useful to manipulate the transform matrix directly - you can easily write functions to scale, rotate and translate the matrix, and then just set the matrix.

_________________
Tristam MacDonald - [swiftcoding]

http://horde3d.org/docs/_api.html#Gener ... _functions
have fun

Volker and swiftcoder,

Thank you very much for your answers. I think I'm going to follow swiftcoder's recomendation and write functions to manipulate the transformation matrix directly as it's the only way to accomplish this task.


Best regards,

Federico Omoto

You can also use the utMath.h by creating a Matrix4f from the pointer you get from e.g. getNodeTransformMatrices()