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 11:42:13 +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: <4B677493-A324-430B-A1C2-8E4962D7206F@noqsi.com> Message-ID: 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> <1355188647 DOT 12937 DOT 14 DOT camel AT localhost> <201212140010 DOT qBE0ABjV023762 AT envy DOT delorie DOT com> <172CCAAB-0423-43EF-8A04-5A9961F1D5B9 AT noqsi DOT com> <201212140122 DOT qBE1MoKM019255 AT envy DOT delorie DOT com> <4B677493-A324-430B-A1C2-8E4962D7206F AT noqsi DOT com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII 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 Precedence: bulk On Fri, 14 Dec 2012, John Doty wrote: > It seems to me than when a human or script draws a conductive object it should know ahead of time what the network affinity of the object is. It is not true and I've already written a counter-example (obstacle, bridge) in this thread, please read back. What is true is: one of the possible strategies of laying out a PCB is the incremental way (expanding traces at the ends until reaching their goal). There are other ways which are more efficient in some cases, and some of those operate with creating floating copper in advance, disconnecting existing copper areas, reconnecting them to different networks, etc. This why a simple first-touch would not work unless you restricted the user to only one method of proceeding with the layout.