X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Tue, 18 Dec 2012 08:21:50 +0100 (CET)
X-X-Sender:	igor2 AT igor2priv
To:	geda-user AT delorie DOT com
X-Debug:	to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From:	gedau AT igor2 DOT repo DOT hu
Subject:	Re: [geda-user] Find rat lines - summary
In-Reply-To:	<CAN0Jx-8mr2XmLHr7AzcTygk205H1H4_X1Y9VcQHw3zia5eGynQ@mail.gmail.com>
Message-ID:	<alpine.DEB.2.00.1212180816280.26605@igor2priv>
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 1212120740300 DOT 26605 AT igor2priv> <CAN0Jx-_+HNgHFNwjNkZRos--yRa9KWLeijjaE7zh5imjp5omuw AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1212150453530 DOT 26605 AT igor2priv> <CAN0Jx-8mr2XmLHr7AzcTygk205H1H4_X1Y9VcQHw3zia5eGynQ AT mail DOT gmail DOT com>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
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 Mon, 17 Dec 2012, Russell Dill wrote:

> On Fri, Dec 14, 2012 at 7:57 PM,  <gedau AT igor2 DOT repo DOT hu> wrote:
>>
>>
>> On Fri, 14 Dec 2012, Russell Dill wrote:
>>
>>> On Tue, Dec 11, 2012 at 11:13 PM,  <gedau AT igor2 DOT repo DOT hu> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I start to lose track of all the diverse ideas. This post is an effort to
>>>> structure the major directions. May it be incomplete, feel free to
>>>> complete
>>>> it.
>>>>
>>>> In case there is a short...
>>>
>>>
>>> Lazy path. Find any path that connects the two shorted objects and
>>> draw that path. The short is somewhere along the path, the user can
>>> follow that path and quickly locate the short.
>>
>>
>> Sorry, this would not work. If you mean to follow the path from all net1
>> nodes to all net2 nodes, then it would just highlight all objects of both
>> nets. If you mean picking one net1 node and net2 node pair randomly, it
>> would show only one short, while there may be multiple.
>
> I'm not talking about highlighting all the objects of both nets. I'm
> talking about drawing a line, rubber band, jagged, or otherwise, that
> follows any path from gnd to vcc. (any pin of net 1 to any pin of net
> 2)

If you have 2 nets with multiple pins with one or more shorts between 
them, and you highlight any (all) paths between any 2 pin combination of 
the two nets, it will mostly highlight everything. Take my simplest 
example, the H shaped (net1 is a b, net 2 is C D):

a --+-- b
     |
C --+-- D

The vertical line segment connects the two nets; short-paths are: a-C, 
a-D, b-C, b-D. If you highlight them, you highlight both nets fully. The 
only things your method exclude are redundant in-net connections:

     +
     |
a --+-- b
     |
C --+-- D
|       |
+-------+

The lower loop between C and D would not be highlighted (if your method
is refined to display all shortest paths; if it's merely all paths, than 
even that would be marked). The upper little vertical line not connecting 
net1 to anything would not be highlighted as it is not part of any path 
from net1 to net2.

Wheter it's highlighting or drawing an extra rubber band line doesn't make 
much difference as too much of the existing copper would be marked.

Regards,

Tibor

- Raw text -