kicad-developers team mailing list archive
Mailing list archive
Re: DRC marker persistence
1) As long as files with markers can be easily shared between people it is
Why isn't "bloated diff" a problem for storing the markers in the project
Would it make sense to have an option to not store the markers?
2) The second scenario of marking a specific error is the least surprising.
How frequently will there be multiple errors of a certain type between the
two same objects? That is a risky scenario, but it is hard to asses without
knowing the chance.
On Tue, Mar 3, 2020 at 11:04 AM Jeff Young <jeff@xxxxxxxxx> wrote:
> Part of the 6.0 DRC architecture is marker persistence. This will allow
> you to work your way through a large set of DRC violations, flagging those
> that have already been checked as exceptions or some-such.
> Two questions:
> 1) Store markers in board file or project file?
> Board file is much easier (in fact currently zero-cost as it’s implemented
> in my tree), but it may cause heartache in “bloated diff” camp? (Note that
> you can always press Delete All Markers when you’re done with DRC, so you
> can choose to not have them in the board file.)
> 2) Should exceptions be of the form “ignore error type X between object Y
> and object Z”, or “this specific error condition is a false-positive”?
> The first is more like a C++ #pragma. The second is arguably “safer”, but
> requires storing hashes of the entire data-state of objects Y and Z.
> Likely expensive to calculate on large boards (and somewhat expensive to
> 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