kicad-developers team mailing list archive

[Nox <noxfiregalaxy@xxxxxxxxx>]

Would not "automatic file version switching" result into even stranger 
situations? i.e. that users of "newer" kicad version would generate 
files which are sometimes compatible and sometimes not without "obvious" 
reason? What normally is done is offering users to save as an older 
fileversion. Do not know how hard this would be to implement in kicad.


Am 21.09.2017 um 02:42 schrieb hauptmech:
> File version issues have hit me a couple times when collaborating. 
> Solutions involve either installing bunch of binaries, stable first, 
> then nightlies, until we find a compatible one, or 'fixing' the file 
> by hand editing to a previous design.
>
> It would be really nice to the user if you used the old file version 
> for designs that had no long names. (or whatever other incremental 
> special case feature change required the version bump)
>
> I know writing code with different types of users in different 
> situations takes extra effort, but everything you guys do so that 
> kicad *just works* on the user side has a huge impact.
>
>
>
>
> On 20/09/17 04:38, Maciej Sumiński wrote:
> > For your information: support for long pad and pin names has been just
> > merged. As the change affects both eeschema and pcbnew, and may result
> > in files that are not loaded correctly with older versions - the file
> > format versions had to be incremented.
> >
> > Regards,
> > Orson
> >
> >
> >
> > _______________________________________________
> > Mailing list:https://launchpad.net/~kicad-developers
> > Post to     :kicad-developers@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe :https://launchpad.net/~kicad-developers
> > More help   :https://help.launchpad.net/ListHelp
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp