Hi Rostislav, as it happens we recently did basically the opposite. We introduced a PersistenceService, where properties can be registered as needing to be written to file [1]. This currently is only taken into account for nrrd files though.
However, I do not know if we want to distinguish between persistent and transient properties for scene files, as - in theory - loading a scene file should return you to the same view you had when saving it. So I would expect the same objects to be selected. Best, Caspar [1] http://bugs.mitk.org/show_bug.cgi?id=19209 -----Ursprüngliche Nachricht----- Von: Rostislav Khlebnikov [mailto:[email protected]] Gesendet: Mittwoch, 26. August 2015 18:43 An: mitk-users Betreff: [mitk-users] Transient properties Hey guys, in my fork I made a simple change to the BaseProperty. Basically, I added the isTransient flag to signify the properties that should not be saved to the scene. In my case the use case is - I set the clipping plane properties to use the unstructured grid mapper to look at the internal structure of an unstructured grid. If the scene is saved with one of these properties active, upon next load the unstructured grid will be cut, which is an undesired behavior. With transient properties this is easily solvable. Another property that I think might benefit from being transient is the "selected" property. When you load the scene it is pretty strange to see some objects in a selected state. What do you think? Rostislav. ------------------------------------------------------------------------------ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users ------------------------------------------------------------------------------ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
