Many of the professional CAD packages do this and it makes collaboration
with people that need to run an older version more difficult.
On 23/02/2019 10:48 AM, Simon Richter wrote:
Hi Seth,
On 22.02.19 18:11, Seth Hillbrand wrote:
It should be easier for new features as they don't need the wrap the
parsing in versioning checks; especially for semantic changes. It may
be more effort when changing underlying structures that are shared
between parsers.
Would it make sense to have a separate "update" process, so the parser
in the loader will never have to deal with legacy files?
When the user opens a file with a lower version number, we branch into
an update wizard that handles updating the file, rewrites it as the new
version and then restarts the load process.
This way we could also keep the schematic element rescue outside of the
loader code.
Simon
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
