www.delorie.com/archives/browse.cgi | search |
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=bccoA9f93zQ0mMVrU30MoxCkOqWpvMTxB84R0h1CYBY=; | |
b=zK+CXA4Ly7OwY0lla/ARIJ/zwz6MRxhcJK4ZjpXNGq/aOk7W45koLvWas/cq2k5XvS | |
md8gSAibFAXvpAW7tpZ0Bnw3hioIis3hdIS7eEDbr+S/BRNIlHR6LzhyrPAJ+6TVSTX7 | |
ThyrAib/7rvwKsZac0nysKmvXwBybgIiswpzB/jZTRHzqmeC7flOsa9wjqEaFmoEAsiM | |
yY2Nu7CxnAPedp1Qqe8cq5L9SOPap96NT0Zo4Jy5/va/4Lpy3JaaG9qRy8iIuV0KabaI | |
+EJs0WGEy/D7qFpbtOlCWvvFs3qXTNTFW3N55gDEiOtCvXX6FUb0zS/CaqiseDwQ2hej | |
CS4w== | |
MIME-Version: | 1.0 |
X-Received: | by 10.194.21.199 with SMTP id x7mr16144340wje.63.1442707879459; |
Sat, 19 Sep 2015 17:11:19 -0700 (PDT) | |
Date: | Sat, 19 Sep 2015 16:11:19 -0800 |
Message-ID: | <CAC4O8c-84zCCvrgRz0gJN3xxe4d+NNcP4m1aX6cj-gi8r+vQmQ@mail.gmail.com> |
Subject: | [geda-user] DRC violation discovery order fix options |
From: | "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> |
To: | geda-user AT delorie DOT com |
Reply-To: | geda-user AT delorie DOT com |
--047d7b5d95cbab7fda0520229ab5 Content-Type: text/plain; charset=UTF-8 well reordering the DRC violations is hard due to lack of model-view separation, there's no list of violations themselves they're just incrementally added to the gui or message showing the violation Options in order of increasing correctness and difficulty: 1. Sort the stuff intended for the gui, as it has links to violations, but then no lesstif fix 2. Make a violation_list or so and reorder to fix it, then go to HIDs from there 3. Fix DRC violation discovery order to be more sensible to begin with. This might actually be pretty easy just using an element list sorted by size rather than ELEMENT_LOOP() in DRCAll. But the DRC code is pretty wild and I'm scared to touch it, it might mess up other categorization in output? --047d7b5d95cbab7fda0520229ab5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><br><div style=3D"">well reordering the DRC violations is = hard due to lack of model-view separation, there's no list of violation= s themselves they're just incrementally added to the gui or message sho= wing the violation</div><div style=3D"">Options in order of increasing corr= ectness and difficulty:</div><div style=3D""><br></div><div style=3D"">1. S= ort the stuff intended for the gui, as it has links to violations, but then= no lesstif fix<br></div><div style=3D""><br></div><div style=3D""><div>2. = Make a violation_list or so and reorder to fix it, then go to HIDs from the= re</div><div style=3D""><br></div><div style=3D"">3. Fix DRC violation disc= overy order to be more sensible to begin with.=C2=A0 This might actually be= pretty easy just using an element list sorted by size rather than ELEMENT_= LOOP() in DRCAll.=C2=A0 But the DRC code is pretty wild and I'm scared = to touch it, it might mess up other categorization in output?</div><div sty= le=3D""><br></div><div style=3D""><br></div><div style=3D""><br></div><div = style=3D""><br></div><div><br></div></div></div> --047d7b5d95cbab7fda0520229ab5--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |