X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Injected-Via-Gmane:	http://gmane.org/
To:	geda-user AT delorie DOT com
From:	Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject:	Re: [geda-user] making DRC less misleading in the presence of shorts, non-routed rats, etc.
Date:	Sat, 03 Oct 2015 04:41:25 +0200
Lines:	36
Message-ID:	<munf8m$u7l$1@ger.gmane.org>
References:	<CAC4O8c_kjtsHhyjH+fPZvhDdPxc+Z+L5RxPy4SpJ8dmcGNKMiA AT mail DOT gmail DOT com>
Mime-Version:	1.0
X-Complaints-To:	usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host:	a89-182-23-235.net-htp.de
User-Agent:	KNode/4.14.1
Reply-To:	geda-user AT delorie DOT com

Britton Kerin wrote:

> * The magic that detects both these condition is AddAllRats().  It
> sets a variety of global state
> for various problems of interest like the above.  So it could be
> called on DRC refresh and used
> to generate DRC reports for these problems.

I'd very much prefer this approach. A warning issued on DRC no matter 
what does not work for me. In the long run, I will get so used to it 
that I routinely ignore it. Everything the DRC complains about should 
refer to actual problems as opposed to potential problems.


> The problem is it's destructive: it resets the rats
> so if the user is trying to work on a subset of the board while
> sometimes doing DRC refresh it's going to be annoying.

You mean a use case where the user manually deletes long range rats to 
get a better feel for the local situation? IMHO, a delete is already a 
crutch in itself. The GUI should instead offer an easy way to mark  
specific rats as "ignored". Ignored rats would not be considered on 
"update rats" connection check. Just like the check already ignores 
nets marked with a star in the net list.  
This should of course be complemented by the ability to un-ignore. 
Ideally it would allow for partial un-ignore. But a simple un-ignore-
all would be sufficient.

I have a feeling, that this kind of ignore might not be easy. Current 
connection check probably does not care for rats but looks at the 
items in the net list. 

That said, how about a checkbox in the DRC dialog to activate 
automatic connection check as part of the DRC run? 

---<)kaimartin(>---

- Raw text -