Hi @Karsten ,

For every node, you create you need to invoke create function, and then if you want it to appear in the DataGraph this node needs to be added to a parent node:

auto camcopy = SAMSON::getActiveCamera()->clone(); // clone the camera camcopy->create(); // create the node document->addChild(camcopy); // add the created camera into the active document /* ... some modifications of the camcopy */ SAMSON::getActiveDocument()->setActiveCamera(camcopy); // set the active camera

Thanks.
It helps.

SBQuantity::radian radianValue(1.5); SBQuantity::degree degreeValue = radianValue * SBConstant::RadToDeg;

Good idea, it will be in 0.8.

Yes thanks. That's what I was looking for.

Hi Khoa, yes, it's always better to create nodes on the heap instead of the stack (i.e. with new). Therefore, you should use a SAMSON pointer (SBPointer) to hold it and destroy the node automatically when the variable gets out of scope.

Dear Patrice, yes, it is planned in a very near future, I didn't have time for the update yet...
Regards,
Sergei

Hi everybody, all my problems with arrows are solved. Thanks very much for your help.

Not instead, in addition: having, at the installation of the App, a list of pre-saved settings, with still the possibility to save and load your own settings.
-- for example, with the Crystal Creator App, having the 'diamond settings', the 'SiGe settings', or for ARPS, some classical configurations of Ef and Er : the '10x speed up settings', '5x speed up settings' ... --

No, sorry, not at the moment.

Hi @Stephane-Redon,

ah yes, it was the depth test. This solves it!

Thanks,
Haichao