Closed GoogleCodeExporter closed 9 years ago
one clue is that it is the SCK/D13 pin, and one cannot drag a wire from the LED
to that pin.
Original comment by irasc...@gmail.com
on 14 Jan 2014 at 11:18
comment 1 is probably a red herring--it is because there is a direct connection
between the parts (arduino pin and LED) in bb view, and
Wire::mouseMoveEventAux() won't allow the arduino pin to be a candidate since
there is already a connection. In PCB view this depends on what layer you trace
from: the top layer has a different part ID, so the arduino pin doesn't show
up; the bottom layer has the same id so it does show up.
I think the code may have to make a distinction if a part is connected to a
part.
Original comment by irasc...@gmail.com
on 14 Jan 2014 at 12:43
@comment2: looks like pcb view now allows a wire to be targeted to a location
that already has a wire.
Original comment by irasc...@gmail.com
on 14 Jan 2014 at 1:02
back to the original topic. the bug disappears when the LED is connected to the
arduino using wires in bb view. I think that connectedMoved or a related
wire-cleanup function is using the direct connection to position one end of the
wire.
Original comment by irasc...@gmail.com
on 14 Jan 2014 at 3:07
r99752f82d1c9 waiting for side-effects before calling it probably fixed.
Original comment by irasc...@gmail.com
on 15 Jan 2014 at 7:06
Original comment by irasc...@gmail.com
on 18 Jan 2014 at 12:02
Issue has moved to new issue tracker at github. Please continue the discussion
at https://github.com/fritzing/fritzing-app/issues
Original comment by andre.knoerig@gmail.com
on 23 Sep 2014 at 3:44
Original issue reported on code.google.com by
irasc...@gmail.com
on 14 Jan 2014 at 11:13