traces can become detached from parts after some routing takes place

[GoogleCodeExporter]

After building a sketch from scratch today (so it's not an old file
problem), i've encountered a bug in the pcb view where parts are not
attached to their traces.

This could be a load issue.  I made 2 versions of the file (trafficlight2
and trafficlight3). Trafficlight3 was made from a saved version of
trafficlight 2.

I found this issue after i did a combination of hand routing and
autorouting on trafficlight2, but I am not yet sure what will reproduce the
problem.  Will try to reproduce it to see if i can pinpoint the steps.

Original issue reported on code.google.com by jenn...@gmail.com on 17 Feb 2009 at 5:25

[GoogleCodeExporter]

not sure when it happened, but looking at trafficlight3, the traces are really 
messed
up: they're missing one or both of their connectors

Original comment by irasc...@gmail.com on 17 Feb 2009 at 5:44

[GoogleCodeExporter]

looks likely that Jenny figured this one out: if you marked a chained wire with
"don't autoroute", the others in the chain weren't also marked.  Clicking 
autoroute
at that point would delete all the chained wires except the marked one.   r2491 
fixes
the marking problem.  lowering priority on this, but keeping it open, in case 
the bug
shows up again 

Original comment by irasc...@gmail.com on 25 Feb 2009 at 11:01

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by irasc...@gmail.com on 25 Feb 2009 at 11:05

• Changed state: ProbablyFixed

[GoogleCodeExporter]

There was a second bug here: if you hand routed some traces, then autorouted, 
then
undid the autorouting, the hand traces were disconnected from their parts.  
Fixed in
r2582

Original comment by irasc...@gmail.com on 6 Mar 2009 at 5:19

[GoogleCodeExporter]

Haven't seen this since the previous comment, so that fix seems to have taken 
care of 
it.

Original comment by irasc...@gmail.com on 18 Jun 2009 at 6:06

• Changed state: Fixed