X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Cam-AntiVirus: no malware found X-Cam-SpamDetails: not scanned X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Message-ID: <1355011808.19390.8.camel@localhost> Subject: Re: [geda-user] Find rat lines From: Peter Clifton To: geda-user AT delorie DOT com Date: Sun, 09 Dec 2012 00:10:08 +0000 In-Reply-To: <20121208112649.388a9d22@jive.levalinux.org> References: <20121204183305 DOT 6b04c0dc AT jive DOT levalinux DOT org> <20121208112649 DOT 388a9d22 AT jive DOT levalinux DOT org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.0-0ubuntu3 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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 Sat, 2012-12-08 at 11:26 +0100, Levente Kovacs wrote: > Please note that when I start to draw a line from a copper object, highlighting > works as before. This might help find the problem. That behaviour was deliberately left, as it is required by auto-enforce-drc. (You will also find the "Find" button in the GTK HID netlist window still has the old behaviour too I think). I have worked up a test-case for the original issue, and having looked at it closely, one key issue we should fix is that bad rat-lines are being added which compound the shorted mess. I'm hoping to work up a more elegant fix than reverting the entire change as I don't want to back out the ability to find "just" the physically connected copper. I noted whilst creating my test-case layout that this can be achieved by erasing the rat-list before hitting "f", but given our future desires for always on, auto-updating rat-lines, I'm hesitant to rely on it as the entire solution. ETA for a big rework will be some time during next week. If I can't get it done by the end of the week, I'll revert the change. (Until then, if you hate the current behaviour, you can apply a local revert of commit 764c3560a722c768a7048f5c70811ec363862882). Regards, -- Peter Clifton Clifton ElectronicsClifton Electronics