Kai Pastor

While the extra map color is great for the ad-hoc implementation, I wonder if this kind of visual feedback shouldn't better be realized only by adding (and using) explicit distance...

- The unstable version already creates additional linebreaks in the regular, compact *.omap* files, for better use in version control. - The 'non-map' data is another story. At least undo...

FTR the request for XML format documentation is tracked in #182.

When you add/remove a color, it will trigger changes in a number of symbols. When you add/remove a symbol, or changes symbol order, it will trigger changes in a number...

@jmacura If you want to process the XML, you should better use the `.xmap` variant, due to its verbosity. The `.omap` variant is optimized for fast saving and loading, and...

> The barrier elements are used when a file format change would cause serious trouble (crash, misrepresentation) with slighly older versions of the software. This is easy to handle when...

> I think this kind of metadata (like open files, views, zoom settings) is typically stored in a separate file by IDE-s and such. Not sure if this might apply...

> The file will be large, and apparently includes undo information, zoom level, view and such. Could not find a description of the file format. Saving undo information can be...

> It seems as some `object/tags`-child nodes are swapping places. This adds unnecessary changes in the commit history. It would be nice to not re-ordering the `tags`. Indeed. This is...

> Then a quick fix would be to order the tags alphabetically every time you save. Sorting everytime you save is too expensive. For now, I switched away from `QHash`...