Hi All, On 11/04/16 07:37, Wayne Stambaugh wrote: > Let's slow down and think about this a bit. I'm not sure that this is > the best way to resolve this. Let me chew on it a bit and I will get > back to you. I've been busy today so hopefully by tomorrow I'll have an > answer. Wayne, Off the cuff I'd propose a single "used features" block in the file format. This would purely be a list of features that are used by this file. then it's easy for the loading software to confirm what it supports eg: roundrect-1, angletext-33 the appended number can be used to differentiate between non backwards compatible versions of a feature
This would be fairly easy to implement, and trivial to test at file load The hardest part would be spending the time to go through and define the struct to the project that records every feature we care about. Although that could be done by only adding features to that struct when a change is made from now on. Regards David G > Thanks, > > Wayne > > On 4/10/2016 12:36 PM, jp charras wrote: >> Le 10/04/2016 16:11, Chris Pavlina a écrit : >>> I like the idea. It'll take some work to implement properly, though. I can >>> start working on it, but it will likely be at least a week before I have >>> anything. >> Thanks you to make me very happy ... >> >>> On Sun, Apr 10, 2016 at 04:05:42PM +0200, jp charras wrote: >>>> Le 10/04/2016 15:31, Chris Pavlina a écrit : >>>>> So - would you be happy with me just changing that to a warning that can >>>>> be >>>>> clicked through instead of an error, and rewriting the message a bit to >>>>> agree? >>>>> >>>> I'll be more happy. >>>> >>>> But I'll be really very happy if a dynamic version numbering is also >>>> added, rather a fixed arbitrary >>>> number. >>>> >>>> Currently the version is 4. >>>> If a method is added (something like GetMinimalVersionNumber()) to all >>>> board items (tracks, texts >>>> footprints, pads...), each item can return the needed minimal version to >>>> be read in file. >>>> Currently they could return 4, but for a pad, if its type is rounded rect >>>> it will return 20160410, >>>> and therefore its footprint parent returns 20160410 (or 4 if no rounded >>>> rect pad is found) >>>> >>>> Before writing the file, just run BOARD::GetMinimalVersionNumber() to know >>>> the actual needed version. >>>> >>>> -- >>>> Jean-Pierre CHARRAS >> > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
