as there are discussions on serialization currently going on I also wanted to add one thing:
I am using an .mitk project file quite often to recover the state of my plugin. Sometimes for debugging, sometimes as interface between two plugins. Let me explain the latter: one plugin A creates a certain setup of data nodes in the DataStorage and the next plugin B consumes this data and processes the data. So I should be able to store the project after processing plugin A into an .mitk file and close and open the Workbench and load the project again to continue with plugin B.
But: when I save a surface node the geometry of the surface is applied to every vertex in the surface and this is stored to file. When I load the surface it is displayed at the same location as before but the node is different. The geometry equals identity and the vertices are modified obviously. The thing is, that plugin B uses the geometry of the surface and if this one is not set or not as expected, the result is incorrect.
So would there be a way to differ between saving an .mitk project (and then to also save geometry data as well and not to change vertices) AND saving a regular .stl (...) file by incorporating the geometry into vertices as that file format doesn't contain a container for this information? That would assure that a saved DataStorage with a surface node equals a loaded one.
I would also contribute those changes once they are agreed upon.
Best Regards!
Ingmar
------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds
_______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
