Description:
Loading scenes that were saved with previous releases (of MITK) creates issues regularly. We should come up with ideas on how to improve stability.
Use-Case:
Currently, interpretation of properties changes, e.g. re-definition or a property value from int to float, or renaming a property. These changes are welcome since properties are still not named regularly. However, this creates complications with “old” scene files because all of a sudden, visualization is different or data is interpreted differently. This creates frustration with users!
Implementation:
Ideas welcome. Basically we would need to define a canon of reference scenes that are created and saved for each release. All of those files from previous releases would need to be loaded with the current release, and we’d have to (manually?) verify that they appear equal. If there are differences, readers must be enhanced with fallback behavior or at least warnings and errors..
(the above is just a very initial idea, but one of the most pressing issues that I hear of)