X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ttHWs4CSBcbIBzezcUTucQLnb79Td1H1I92zb62P9pM=; b=BphpzVGJli82JbwfsiSI/1/7LkAy4SQXrGfipt3RB7o3k1V04I76a4YcqDDmpS4N0J 4FEQZydvrrFt93qhGWCMG66fimoWnfoWPlcOStKdSoj0bf98MIA6kf7yXP1eQwSGiuLG f4UjFfJEsKcLnk2DvW9l8seQPLHylZY2xIrKJW+YgYB+LJ8frT4qXDOFTpZnhCQwTFm+ i1GAQNg3X1rTt47n6SmlFHVDpVfpH9qx5i3udhvqs+/7tkoi448OBaNOse7WYzSQ7jCi yglERhMH8fEQcNx+OGG+ZCqq9HuSI2iI1A5ewJxifak3nGHjc9UJhp+Ia4GSxA5prjAX hPuw== MIME-Version: 1.0 X-Received: by 10.194.8.227 with SMTP id u3mr18619667wja.38.1443828075781; Fri, 02 Oct 2015 16:21:15 -0700 (PDT) Date: Fri, 2 Oct 2015 15:21:15 -0800 Message-ID: Subject: [geda-user] making DRC less misleading in the presence of shorts, non-routed rats, etc. From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=047d7b5d9c0792e74b0521276be2 Reply-To: geda-user AT delorie DOT com --047d7b5d9c0792e74b0521276be2 Content-Type: text/plain; charset=UTF-8 At the moment DRC catches near-shorts (trace too close to another), but is completely silent when there's an actual short. Same thing for not-routed rats sort of: a marginal connection is reported, a completely missing one is not. I remember being unpleasantly surprised by this so I'd like to do something about it. Possible approaches and related questions I have: * The simplest option is to just always put a DRC entry in the list explaining the issue and instructing the user what to do to make sure everything is ok. I'm leaning towards this option. It's slightly less good but way easier to implement and I think addresses the issue well enough. * The magic that detects both these condition is AddAllRats(). It sets a variety of global state for various problems of interest like the above. So it could be called on DRC refresh and used to generate DRC reports for these problems. The problem is it's destructive: it resets the rats so if the user is trying to work on a subset of the board while sometimes doing DRC refresh it's going to be annoying. Is there a non-destructive equivalent? Would it be simple to create one? --047d7b5d9c0792e74b0521276be2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

At the moment DRC catches near-shorts = (trace too close to another), but is completely silent when there's an = actual short. =C2=A0

Same th= ing for not-routed rats sort of: a marginal connection is reported, a compl= etely missing one is not.

I = remember being unpleasantly surprised by this so I'd like to do somethi= ng about it.

Possible approa= ches and related questions I have:

=C2=A0 * =C2=A0The simplest option is to just always put a DRC = entry in the list explaining the issue and
=C2=A0 =C2=A0 =C2=A0in= structing the user what to do to make sure everything is ok.=C2=A0 I'm = leaning towards this=C2=A0
=C2=A0 =C2=A0 =C2=A0option.=C2=A0 It&#= 39;s slightly less good but way easier to implement and I think addresses t= he issue
=C2=A0 =C2=A0 =C2=A0well enough.

=C2=A0 * The magic that detects both these = condition is AddAllRats().=C2=A0 It sets a variety of global state
=C2=A0 =C2=A0 =C2=A0for various problems of interest like = the above.=C2=A0 So it could be called on DRC refresh and used
=C2=A0 =C2=A0 =C2=A0to generate DRC reports for these problems.=C2= =A0 The problem is it's destructive: it resets the rats
=C2=A0 =C2=A0 =C2=A0so if the user is trying to work on a subset of t= he board while sometimes doing DRC refresh it's =C2=A0 =C2=A0 =C2=A0=C2= =A0
=C2=A0 =C2=A0 =C2=A0going to be annoying.=C2=A0 Is= there a non-destructive equivalent?=C2=A0 Would it be simple to create one= ?

=C2=A0

--047d7b5d9c0792e74b0521276be2--