X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Thu, 13 Dec 2012 20:22:50 -0500 Message-Id: <201212140122.qBE1MoKM019255@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: <172CCAAB-0423-43EF-8A04-5A9961F1D5B9@noqsi.com> (message from John Doty on Thu, 13 Dec 2012 18:16:34 -0700) Subject: Re: [geda-user] Find rat lines 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> 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 > To expand on my confusion, I cannot understand how this could be > difficult An example of the difficulty: the user selects a region of items on the pcb and moves them to the other side, or even just moves them elsewhere. The simplistic "first touch" netlist ownership method fails miserably with those simple commands, because a huge number of connections change simultaneously. Even something as simple as adding a single trace could "short" multiple existing subnets, and if some of those subnets have been assigned to nets but some subnets are as yet unassigned (because they have yet to connect to something known to be in the netlist), you get lots of arbitrary choices to be made about how everything needs to be resolved.