Mail Archives: geda-user/2015/10/04/16:54:23
--f46d0445182f8b1da205214d99a2
Content-Type: text/plain; charset=UTF-8
On Sun, Oct 4, 2015 at 2:27 AM, Markus Hitter (mah AT jump-ing DOT de) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> Am 04.10.2015 um 00:46 schrieb Britton Kerin:
> > On Sat, Oct 3, 2015 at 1:07 AM, Markus Hitter wrote:
> >
> >> Am 03.10.2015 um 01:21 schrieb Britton Kerin:
> >>
> >>> At the moment DRC catches near-shorts (trace too close to another), but
> >> is
> >>> completely silent when there's an actual short.
> >>
> >> That's expected, that's what DRC does. Checking for shorts means to
> >
> > When I started, it was not at all expected. Its weird that you can go
> from
> > almost-short, to short, and thereby make a violation vanish.
>
> What I mean is that it's pointless to try to fix DRC code for detecting
> shorts. DRC techniques can't do this. Comparing connections with the
> netlist can, and that's what "optimize rats" already does. No need to
> duplicate existing code.
>
> All you have to do is to make sure and intuitive that users check not
> only for DRC violations, but also for shorts. Following the code in
> ActionAddRats() in action.c shows how to do this.
>
> I'd try to catch the output of AddAllRats() into a buffer for displaying
> it in the DRC window. Perhaps only the first 1024 bytes or something.
> Some new GUI code, reuse of short-checking code, mission accomplished.
>
> BTW., this will also check for missing connections, which are certainly
> also a reason to not send a board to the manufacturer.
Yes, I said so already. The branch I made mentions it also.
I'm moving on from this issue. If anyone wants to do any of the much
harder things proposed instead of what I put in
home/bkerin/drc_warning_for_noobs that would be great, but I submit that
until that time the simple change in that branch is better than nothing.
--f46d0445182f8b1da205214d99a2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sun, Oct 4, 2015 at 2:27 AM, Markus Hitter (<a href=3D"mailto:mah AT ju=
mp-ing.de">mah AT jump-ing DOT de</a>) [via <a href=3D"mailto:geda-user AT delorie DOT co=
m">geda-user AT delorie DOT com</a>] <span dir=3D"ltr"><<a href=3D"mailto:geda-=
user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>></span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">Am 04.10.2015 um 00:46 schrieb Britt=
on Kerin:<br>
<span class=3D"">> On Sat, Oct 3, 2015 at 1:07 AM, Markus Hitter wrote:<=
br>
><br>
>> Am 03.10.2015 um 01:21 schrieb Britton Kerin:<br>
>><br>
>>> At the moment DRC catches near-shorts (trace too close to anot=
her), but<br>
>> is<br>
>>> completely silent when there's an actual short.<br>
>><br>
>> That's expected, that's what DRC does. Checking for shorts=
means to<br>
><br>
> When I started, it was not at all expected.=C2=A0 Its weird that you c=
an go from<br>
> almost-short, to short, and thereby make a violation vanish.<br>
<br>
</span>What I mean is that it's pointless to try to fix DRC code for de=
tecting<br>
shorts. DRC techniques can't do this. Comparing connections with the<br=
>
netlist can, and that's what "optimize rats" already does. No=
need to<br>
duplicate existing code.<br>
<br>
All you have to do is to make sure and intuitive that users check not<br>
only for DRC violations, but also for shorts. Following the code in<br>
ActionAddRats() in action.c shows how to do this.<br>
<br>
I'd try to catch the output of AddAllRats() into a buffer for displayin=
g<br>
it in the DRC window. Perhaps only the first 1024 bytes or something.<br>
Some new GUI code, reuse of short-checking code, mission accomplished.<br>
<br>
BTW., this will also check for missing connections, which are certainly<br>
also a reason to not send a board to the manufacturer.</blockquote><div><br=
></div><div style=3D"">Yes, I said so already.=C2=A0 The branch I made ment=
ions it also.</div><div style=3D""><br></div><div style=3D"">I'm moving=
on from this issue.=C2=A0 If anyone wants to do any of the much harder thi=
ngs proposed instead of what I put in home/bkerin/drc_warning_for_noobs tha=
t would be great, but I submit that until that time the simple change in th=
at branch is better than nothing.</div><div><br></div></div></div></div>
--f46d0445182f8b1da205214d99a2--
- Raw text -