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=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-type:content-transfer-encoding;
	bh=S+GGRL3oM2usxXdM5zGvcCOmi94SV5yfa9vkgcwaMwA=;
	b=CSN6IwXK3iYuSDDlXxDydH4XEafR1AyTVo6meY0g4CaBs8WMa6ncAd6jARo7Dyv6VD
	qB+mNoFC6hKpgP+1bY4o3ky2gNAXAsG+xd8NpLbnwq8fJMN16vuV48U8dhhHh/aPKguq
	RMF7RJ8lsJQ7eBmdQ5BADKJJem07QMK6XnZuPBdF4MzuUkKb2CgSudL6w0XbqfyXitZ1
	FqeZ8Vpar1fiRKuEtQ3oXoD2UBc4WGoS3qUCcI/J9BydwG+vpRudzldu3aFv/LgzG5iB
	6N+LTC9B5XzmBEsVe498b7LrEpN6pz6UrbpyQ22s9G79ZV3FBYztmNzdxwFzOUED5rFK
	PXWA==
X-Received:	by 10.194.248.198 with SMTP id yo6mr7214967wjc.66.1443944814232;
	Sun, 04 Oct 2015 00:46:54 -0700 (PDT)
Date:	Sun, 4 Oct 2015 09:46:49 +0200
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] making DRC less misleading in the presence of
	shorts, non-routed rats, etc.
Message-Id:	<20151004094649.6dc054ec476455fa98afa1c9@gmail.com>
In-Reply-To:	<CAC4O8c8i3xswKjACqGR5=7siEZXU7ZH6Cj_0SoBenB-yn8kCjQ@mail.gmail.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>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

> On Sat, Oct 3, 2015 at 1:07 AM, Markus Hitter (mah AT jump-ing DOT de) [via
> geda-user AT delorie DOT com] <geda-user AT delorie DOT com> 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.  In fact it's
> pretty easy to accidentally create a short while fixing a proximity
> violation.  I happened to catch it before ordering the prototype boards but
> only

I think you are right.

Nicklas Karlsson

- Raw text -