delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2012/12/10/04:15:20

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=dch78IRILjsDdYTn84hEpJ26xOhxDwrPWrE9Oeedepg=;
b=WJe4vh3yzCTDwR9mX+t82kchQdXjiH2d7QL0b50aTqF1+L4UgM4Wmd4dfFlBvqelCN
sTNhqdYEV5nsEtzQ0N2N1LjT9cnW2opAjbhhNuKE1ZL2RtaFdqELcCMpKCe7h7cjhJTp
aUCH5DgxEj1oESBbDUEv0Ju4kTuEVC3Dbv7nPsndNJX0OW/cyP91pCLbbCiH+CNiBtFH
rsPzobFtQCjbyLTAYfBjK4pQIejiDEB1tSkQGfFB9y1w0bnCIDQ2iKrTMXv7aUdFYv58
ud1fQ3P0ydn3zADRVIv8R2D8N8+575UZt17RsTPMgRX5qz0LRK4fdiAuSSvqnuzgDXAq
iqeA==
MIME-Version: 1.0
In-Reply-To: <35569664-3107-4F54-BD56-42EBEB7C0CD7@jump-ing.de>
References: <20121204183305 DOT 6b04c0dc AT jive DOT levalinux DOT org>
<20121208112649 DOT 388a9d22 AT jive DOT levalinux DOT org>
<1355011808 DOT 19390 DOT 8 DOT camel AT localhost>
<alpine DOT DEB DOT 2 DOT 00 DOT 1212090407031 DOT 26605 AT igor2priv>
<20121209164921 DOT 5acd2412 AT akka>
<35569664-3107-4F54-BD56-42EBEB7C0CD7 AT jump-ing DOT de>
Date: Mon, 10 Dec 2012 10:13:40 +0100
Message-ID: <CACwWb3A7pBkWcVvGuRfEL4LTpzaGefo-T1p0VuC1Q042owcD=Q@mail.gmail.com>
Subject: Re: [geda-user] Find rat lines
From: Levente <leventelist AT gmail DOT com>
To: geda-user AT delorie DOT com
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

--f46d0445170d2ce67b04d07bfbc5
Content-Type: text/plain; charset=ISO-8859-1

+1

On Mon, Dec 10, 2012 at 3:02 AM, Markus Hitter <mah AT jump-ing DOT de> wrote:

>
> Am 09.12.2012 um 16:49 schrieb Kai-Martin Knaak:
>
>  gedau AT igor2 DOT repo DOT hu schrieb am  9. December 2012:
>>
>>  However, if we rephase the question from "what causes the short" to
>>> "what user modification introduced the short"
>>>
>>
>> +1. I tend to resolve difficult shorts by simply going back in the
>> history until update nets does not complain anymore.
>>
>> Protel99 avoids this by a different approach: This EDA checks after
>> every edit for shorts. So the user is notified immediately that an edit
>> causes a violation.
>>
>
> Do you guys never import a bunch of new or renamed components with
> (x)gschem2pcb? In that case neither of these approaches is helpful, you
> start with a big mess and there is no previous unshorted state.
>
> When I actually need the behaviour described above, I open the log window
> and hit O after about every change. Shorts can be seen at a glance, they
> produce more text that just a "x ratlines remaining".
>
>
> my $0.02
>
> Markus
>
> - - - - - - - - - - - - - - - - - - -
> Dipl. Ing. (FH) Markus Hitter
> http://www.jump-ing.de/
>
>
>
>
>
>

--f46d0445170d2ce67b04d07bfbc5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1<br><br><div class=3D"gmail_quote">On Mon, Dec 10, 2012 at 3:02 AM, Marku=
s Hitter <span dir=3D"ltr">&lt;<a href=3D"mailto:mah AT jump-ing DOT de" target=3D=
"_blank">mah AT jump-ing DOT de</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
<br>
Am 09.12.2012 um 16:49 schrieb Kai-Martin Knaak:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">
<a href=3D"mailto:gedau AT igor2 DOT repo DOT hu" target=3D"_blank">gedau AT igor2 DOT repo DOT h=
u</a> schrieb am =A09. December 2012:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
However, if we rephase the question from &quot;what causes the short&quot; =
to<br>
&quot;what user modification introduced the short&quot;<br>
</blockquote>
<br></div><div class=3D"im">
+1. I tend to resolve difficult shorts by simply going back in the<br>
history until update nets does not complain anymore.<br>
<br>
Protel99 avoids this by a different approach: This EDA checks after<br>
every edit for shorts. So the user is notified immediately that an edit<br>
causes a violation.<br>
</div></blockquote>
<br>
Do you guys never import a bunch of new or renamed components with (x)gsche=
m2pcb? In that case neither of these approaches is helpful, you start with =
a big mess and there is no previous unshorted state.<br>
<br>
When I actually need the behaviour described above, I open the log window a=
nd hit O after about every change. Shorts can be seen at a glance, they pro=
duce more text that just a &quot;x ratlines remaining&quot;.<br>
<br>
<br>
my $0.02<div class=3D"HOEnZb"><div class=3D"h5"><br>
Markus<br>
<br>
- - - - - - - - - - - - - - - - - - -<br>
Dipl. Ing. (FH) Markus Hitter<br>
<a href=3D"http://www.jump-ing.de/" target=3D"_blank">http://www.jump-ing.d=
e/</a><br>
<br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br>

--f46d0445170d2ce67b04d07bfbc5--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019