Cura/plugins/LegacyProfileReader
Ghostkeeper 6ad682b00d
Don't serialise legacy profile via Profile instance
That profile instance was being explicitly set to version 1 (but then serialised as version 4) and then deserialised with upgrade, so the upgrade was thinking it was upgrading from version 1 to 4, but it was actually upgrading a file which was already at version 4. We shouldn't use the Profile() instance at all but just perform the upgrade on simple string data generated by the configparser.
This also updates the format to the newest version (since that was easiest for me to reimplement) but we don't need to ever update this again because it gets passed through the version upgrade system, which upgrades it from version 4000005 to the latest version in the future.

Contributes to issue CURA-5929.
2018-11-12 12:02:49 +01:00
..
__init__.py Changing AGPLv3 to LGPLv3 2017-09-28 13:00:43 +02:00
DictionaryOfDoom.json Change target version of the dictionary of doom to be compliant with the 2018-03-27 11:44:24 +02:00
LegacyProfileReader.py Don't serialise legacy profile via Profile instance 2018-11-12 12:02:49 +01:00
plugin.json Increase plugin API version to 5 2018-08-27 13:59:00 +02:00