kicad-developers team mailing list archive

[Seth Hillbrand <seth@xxxxxxxxxxxxx>]

Jeff-

Am Sa., 1. Sep. 2018 um 10:23 Uhr schrieb Jeff Young <jeff@xxxxxxxxx>:

> FWIW, DRC now handles collisions with copper arcs, and zone cutouts for
> copper arcs.
>

That's great news.  I missed when that went in.  How does it determine the
net of the copper?  Or does it just flag the arcs overlapping anything?

What’s still missing is the Connection Algorithm (because they’re arcs and
> not tracks).  That also means the DRC clearance calculations are one-sided
> as they only take into account the clearance of the colliding track or the
> zone (as the arcs are assumed to have a 0 clearance).
>

Right, there's also some deep work in TRACK (and probably more) to support
more than segments.



> And then there’s the question of editing.  How do you drag tracks with
> curved corners?  Would one expect the PNS router to create curved tracks
> under some set of conditions?
>

I would love to document our expectations of this in written plan before
anyone starts coding.  The UX requirements will drive how this is designed,
to some extent.

Best-
Seth



>
> Cheers,
> Jeff.
>
>
> On 1 Sep 2018, at 05:41, hauptmech <hauptmech@xxxxxxxxx> wrote:
>
>  On 1/09/18 00:44, Wayne Stambaugh wrote:
>
> I don't ever remember myself or JP not being interested in round traces.
>  It's just been a matter of priorities and manpower.
>
> With arc tracks I had an itch to scratch and tried twice to get core dev
> buy-in (https://lists.launchpad.net/kicad-developers/msg27878.html,
> https://lists.launchpad.net/kicad-developers/msg29877.html) so that I
> could put together a patch that used an approach that would get accepted.
> When suggesting options for modifying class TRACK I got silence from the
> core devs and took the hint. C'est la vie.
>
> I do remember
> being pretty firm on ensuring that the gerber plotting and DRC are
> correct before the drawing tools and file format changes go live.  The
> reason for this should be obvious.  Fixing the DRC is in the v6 road map
> so that would be the best place to start for someone who has a lot of
> free time.
>
>
> Why limit development to people that have a lot of free time?
>
> The v6 roadmap has not been updated in a long time. What remains to be
> fixed? Looking at the commit history to DRCish files, it looks like there
> is plenty of activity going on. Can we ask those people to touch the
> roadmap and update it?
>
> There have been some ambitious ideas posted on this list about what DRC
> needs to be, as well as bugs and blueprints. They are not in the v6
> roadmap. Should any of them be added?
>
>
> The amount of work to implement this is not going to be
> trivial and I will expect the design and quality of the DRC code changes
> to be high.
>
> Cheers,
>
> Wayne
>
>
> _______________________________________________
> 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
>