Correct t3 subsystem export order

[blitzmann]

Apparently EVE cares which order they are presented in:

https://forums.eveonline.com/default.aspx?g=posts&m=4703937#post4703937

Untested and unconfirmed at the moment.

[blitzmann]

I've confirmed that this is indeed an issue. Furthermore, it seems to be a bug on CCPs side, as I cannot fathom why they would allow a fitting to save correctly and show up correctly, but the order that the modules was exported is important.

Affects both DNA (HTML) and XML exports

[blitzmann]

Looked into it, and I'd like to do this properly by modifying the module position when the subsystem is added rather than hacking some kind of sorting into the export code.

Every subsystem has a subSystemSlot attribute, which takes on the following int:

125 - Electronics
126 - Defensive
127 - Engineering
128 - Offensive
129 - Propulsion

Which is also the order in which they need to be placed.

Add these values with the Module module (where definitions of State, Slot, etc already reside) and upon adding a module, check if it's a subsystem and, if so, check for it's proper placement. Disallow module swapping on Subsystems

[blitzmann]

Actually, refreshing my memory on how module positions are set in the backend, to do this 'properly' would require a bit more work than I initially thought. We would have to modify the module appending (which handles assigning positions based on :magic:). I think I'll make a quick fix in just export itself, and in spare time look into making it a bit better by modifying the actual positions (which isn't really required for Pyfa to properly function)

[blitzmann]

(Accidentally closed with commit)

Fixed to my knowledge, however I would like to do a few tests that require access to SISI. Specifically, I want to make sure that location of the subsystems in the DNA export is not specific and only order is (ie, does the client freak out when subsystems come before drones?). For this I will have to use SISI as I do not have any offensive T3s with drones and stuff that I can easily test with on TQ. I'm away from my dev machine atm, so hopefully I'll get around to testing this in the next couple days.