kicad-developers team mailing list archive
Mailing list archive
Re: V6 merge update
I have a patch for treating track clearance the same as track width. The
user can already specify a track width that is an exception to the
netclass width, and now do the same for clearance. (
It's bitrotted for a year so I'd want an Ok before putting in the work
to bring it up to date.
Thomasz raised a concern at the time on a related, smaller, patch:
- we are planning to overhaul the clearance/design rules system in V6.
Storing the clearance *DIRECTLY* for each track segment/via will
conflict with any more sophisticated design rule management system.
Noting that clearance is only stored on segments that are exceptions to
the netclass (or whatever DRM might be added); I disagree with this.
Happy to discuss it if the concern remains.
I believe the patch functionality and UI changes would not overlap any
design rules management system as it's focused on manual control of
clearance only. Some (maybe all, I don't recall exactly) of the UI
elements are only present when manual clearances are being used in the
design so there is little impact on users that don't use it.
On 22/02/2019 9:21 AM, Wayne Stambaugh wrote:
Since we are nearing the 5.1.0 release, I want to get an idea of what
major merges are ready to go once 5.1 is branched. I know Jon's netlist
code is ready to merge and I'm pretty sure that should be the first big
merge. Does anyone else have any major changes they want to merge as
soon as v6 starts? I would like to get an idea of what changes to
expect so we can avoid any serious merge chaos. Please let me know what
you have in the queue so I can get an idea of how we should proceed with
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