kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #14600
Re: Edge.Cuts layer in the module editor
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/03/2014 10:36 PM, Wayne Stambaugh wrote:
> On 9/3/2014 12:33 PM, Brian Sidebotham wrote:
>> I think we could do it in a similar fashion to EESCHEMA (it's a
>> more pleasant experience when things work in a similar way) Any
>> vertexes on the Edge.Cuts layer that do not match *exactly*
>> should be highlighted with a square centred on the disconnected
>> vertex(es).
>>
>> Secondly, we can apply similar logic to pads being magnetic to
>> tracks by having Edge.Cuts vertexes being able to snap to
>> currently off-grid Edge.Cuts vertexes as well as to the grid.
>>
>> This way anyone can guarantee they have at least connected all
>> of their Edge.Cuts drawings. Secondly, part of the DRC check can
>> also list disconnected Edge.Cuts vertexes - because that should
>> at least be a warning, if not an error.
>>
>> I don't think there's any reason to have disconnected vertexes on
>> the Edge.Cuts layer is there? Perhaps for drawing a rout line,
>> but then I draw a rectangle with the correct width of the router
>> bit I want used so it is less ambiguous.
>>
>> Best Regards,
>>
>> Brian.
All that sounds good, but demands more work than I initially expected,
so it may take time. Recently the time that I can devote to KiCad
development is a bit constrained.
The PNS router uses its internal model to implement snapping,
therefore I wonder if it would not be better to delay snapping until
the current model is upgraded. The rest of proposed changes should be
possible to implement without any other dependencies.
> Excellent suggestions. This seems like a reasonable path forward.
> I really like the snapping idea as an easy way to close the
> vertices. I always have to manually go back and use the segment
> properties to make sure each vertex ends at the same point if I
> don't get them right the first time. Should I add this to the road
> map? It seems like a good candidate.
Good ideas are worth noting and putting to the plan. That way they
will not be forgotten.
Regards,
Orson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJUCCrHAAoJEBRwGu1hpbJ1MnoH/0i8Y99JoK/R0u46oZC7zn5I
uo3NZ8elAULwjXfwoRE546qwMTPXGVYBSayXeBuIjeE0nre0n0eddaSTD57dZriI
HnmuladHQ2iWbnCZfhzrUYfKQ/S+Z9a2H+Ur8Xi3lhmcpTEe5K/MmmFtjIhHd2h4
EaCFd/b89fHepXnuWtWL03cdoq/hsLOyYWXMG3AMIVwECXazKxONXz18jo6BzAca
4YH5vJaHDy7S4Gif/OECZSebQIg14PMRXTzZRL7/gAeZ+aBMf7neCCZrzr/bbpnW
eQLKa+4mt5HTk51AnrZZEOCeVYY719LauKRc+RI9UYuAr0E+t0YRqiULVj9rye0=
=Frip
-----END PGP SIGNATURE-----
Follow ups
References
-
Edge.Cuts layer in the module editor
From: Maciej Sumiński, 2014-09-01
-
Re: Edge.Cuts layer in the module editor
From: Wayne Stambaugh, 2014-09-02
-
Re: Edge.Cuts layer in the module editor
From: jp charras, 2014-09-02
-
Re: Edge.Cuts layer in the module editor
From: Cirilo Bernardo, 2014-09-02
-
Re: Edge.Cuts layer in the module editor
From: Lorenzo Marcantonio, 2014-09-03
-
Re: Edge.Cuts layer in the module editor
From: Lorenzo Marcantonio, 2014-09-03
-
Re: Edge.Cuts layer in the module editor
From: Maciej Sumiński, 2014-09-03
-
Re: Edge.Cuts layer in the module editor
From: Lorenzo Marcantonio, 2014-09-03
-
Re: Edge.Cuts layer in the module editor
From: Maciej Sumiński, 2014-09-03
-
Re: Edge.Cuts layer in the module editor
From: Brian Sidebotham, 2014-09-03
-
Re: Edge.Cuts layer in the module editor
From: Wayne Stambaugh, 2014-09-03