Yes, we have atoms. The 0.8.0 solution will be the best long-term, as we are dealing with large systems and FPS drop a lot when translating or rotating, but for now I will check the ParticlePositionChanged event.
I think I found the problem. Some initialization functions in the constructor of my class were overriding the unserialization. I tried to make a quick fix but when I do static casts in the unserialize function, SAMSON is crashing, so I will modify my constructor and check, it will take a bit though.
My CMakeLists for the Python Bindings version is like you posted above, so I'm not linking in the debug mode. My other branches don't have any reference to Python in the CMakeLists, so they are not linking neither.
I think it should be possible, it will be just an additional line in the launcher script. If we will be shipping Python Scripting with the Python environment, I think we might ship the environment with a bare SAMSON installation so that to use SAMSON Elements, that depend on this environment, the user won't need to install the Python Scripting Element.
In case someone else is in the same situation. I just finished porting our plugin to 0.7.0 and the only changes I had to make were in SAMSON::getProxy (the arguments have changed), and the call functions of the proxies (arguments of SBValue type used to be pointers, now they are passed by reference).
We have still to test it to make sure all functionality is working, but so far it seems that was it.
Looks like your connection to SAMSON Connect - Forum was lost, please wait while we try to reconnect.