Import matrix shuffles design solutions in data structure "dsMap"

There are many things that may be affecting this. One of the more important factors is that the imported (and exported) data structure contains GUI-data (which it shouldn't. See isse #77 ). Another is that the import may be shuffling the data, though this should be resolved by the hash that is resolved immediately after the import is completed. Thus, solving issue #77 might resolve this issue too.

**Old theory of what was causing the issue that may or may not still be interesitng:**
In the MorphMatrix dsMap property the DSs are sometimes shuffled when saving and reimporting. This does not damage the file, but it prompts the user that the matrix "has been changed", even though it hasn't.

This could possibly be solved by importing each DS in the order of its position (sorting them before importing them).

Start by reviewing issue #77 and tracing the dsMap import/export path; the issue names no files or tests. Compare imported ordering with the post-import hash behavior, and consider the work complete when an unchanged matrix no longer reports that it changed and GUI data is excluded if that is the intended resolution.

Written by the indexing model from the issue text.