delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2012/12/14/04:07:08

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Fri, 14 Dec 2012 10:15:57 +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
In-Reply-To: <6E00459F-C749-4DE5-B182-44A8623E70E8@noqsi.com>
Message-ID: <alpine.DEB.2.00.1212141012260.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 1212090407031 DOT 26605 AT igor2priv> <1355188647 DOT 12937 DOT 14 DOT camel AT localhost> <A7B4EDBD-3704-4837-9350-A16559C60A2A AT noqsi DOT com>
<1355442697 DOT 2993 DOT 14 DOT camel AT localhost> <008677C3-7BA0-4B7D-B8E7-D0A5B2CCC573 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1212140350530 DOT 26605 AT igor2priv> <898C7D41-7B55-4D61-9CC6-7ABB560C144E AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1212140458230 DOT 26605 AT igor2priv> <5189151C-7C93-4AD6-A154-185C8F7AC203 AT noqsi DOT com>
<alpine DOT DEB DOT 2 DOT 00 DOT 1212140537520 DOT 26605 AT igor2priv> <6E00459F-C749-4DE5-B182-44A8623E70E8 AT noqsi 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 Fri, 14 Dec 2012, John Doty wrote:

>
> On Dec 13, 2012, at 9:40 PM, gedau AT igor2 DOT repo DOT hu wrote:
>
>>
>>
>> On Thu, 13 Dec 2012, John Doty wrote:
>>
>>> You miss my point: the fact that the info isn't generally available is part of the confusing design of the tool.
>>
>> It is not available when it gets invalid (change in the netlist). This is a more theoretical question, not an implementation detail of PCB. Could you propose a solution for that, assuming your dream-PCB remembers anything you want and represents copper the way you want?
>
> In red, highlight every point where conductors with different network affiliations touch. Then, after dramatic changes to the netlist, the user will see a lot of red.

How do you _exactly_ define/calculate network affiliation? That was the 
original problem for the non-history case, so don't just assume it is 
solved, solve it.

Just highlighting everything what is in short is possible with the old 
behaviour: press F over a shorted net. This is exactly what we want to 
refine, as it is not helpful on complex boards.

Regards,

Tibor

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019