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=simple; d=mail.ud03.udmedia.de; h=
	subject:to:references:from:message-id:date:mime-version
	:in-reply-to:content-type:content-transfer-encoding; s=beta; bh=
	K5KAoJTO6+SVo7xqo2uMZHf9iu7AZiYSfM1ucjiiJ/s=; b=iAy5d8hI2kPurogX
	5zzpBCpx6I9vpdsmfiXvalQV1vnd9Xldm1jy3sNhOUotr6U6nspPPzOsIUhiFULx
	qAWMhXaztSAwxBN4FYzMSn1HyMhDvzwi2EAFFRRvaeFvzCPp+nwdhDby8R4PmKls
	cuugnQFs6alf6EBO9wy0L4rbEuA=
Subject:	Re: [geda-user] making DRC less misleading in the presence of shorts,
	non-routed rats, etc.
To:	geda-user AT delorie DOT com
References:	<CAC4O8c_kjtsHhyjH+fPZvhDdPxc+Z+L5RxPy4SpJ8dmcGNKMiA AT mail DOT gmail DOT com>
	<560F9AC7 DOT 3040607 AT jump-ing DOT de>
	<CAC4O8c8i3xswKjACqGR5=7siEZXU7ZH6Cj_0SoBenB-yn8kCjQ AT mail DOT gmail DOT com>
From:	"Markus Hitter (mah AT jump-ing DOT de) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Enigmail-Draft-Status:	N1110
Message-ID:	<5610FEF9.5050307@jump-ing.de>
Date:	Sun, 4 Oct 2015 12:27:05 +0200
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Thunderbird/38.2.0
MIME-Version:	1.0
In-Reply-To:	<CAC4O8c8i3xswKjACqGR5=7siEZXU7ZH6Cj_0SoBenB-yn8kCjQ@mail.gmail.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

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.


Markus

-- 
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. (FH) Markus Hitter
http://www.jump-ing.de/

- Raw text -