While updating Arbed for 2015r4 and 2016r1, I noticed a few strange effects with the XML format vs. Binary format:
The constraints get written in reverse order to the XML, but do not get reversed again while reading the XML back into the IDE. Apart from that being a bit annoying since I cannot so easily validate that Arbed’s output is correct, I wonder if the reversed order has also implications for the project at Runtime, and therefore should be considered a bug?
The binary format contains a new “visi” entry which isn’t represented in the XML format. I hope it has no meaning and can be ignored.