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=simple; d=mail.ud03.udmedia.de; h=
	mime-version:in-reply-to:references:content-type:message-id
	:content-transfer-encoding:from:subject:date:to; s=beta; bh=Yay8
	fBN3hTTSm75k18vvQZmlvTbZGrlCtnHz4OuK9Nc=; b=QlgQPgJWjgYAL7GB7DrR
	fRCmmD6kSL+yqvnfM+3rwzzb0eOA9H7sucvy1E6V/7lKxyvX+iadyeKImhKomiMe
	2J0UIbIPehbg9OhuNqh5QZqdJCY5Zq84R29FlHuJv1X75DMb+BtMZ/MBEK24ySzu
	/78fbal+1P8Q/dvS9B9IcW0=
Mime-Version: 1.0 (Apple Message framework v753.1)
In-Reply-To: <20121209164921.5acd2412@akka>
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>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <35569664-3107-4F54-BD56-42EBEB7C0CD7@jump-ing.de>
Content-Transfer-Encoding: 7bit
From: Markus Hitter <mah AT jump-ing DOT de>
Subject: Re: [geda-user] Find rat lines
Date: Mon, 10 Dec 2012 03:02:59 +0100
To: geda-user AT delorie DOT com
X-Mailer: Apple Mail (2.753.1)
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
Precedence: bulk


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/