1.0.6 - Issues with traces being treated as one

bugs
1

Steps I took that resulted in the problem:

connect a trace from one resistor to an other component,

connect a trace from another resistor to the first

attempt to take trace one to the back

both traces went to the back. ???!!!

…

What I expected should have happened instead:

I expected the selected wire not to select both traces and only the one section to go to the back

My version of Fritzing and my operating system:

this is version 1.0.6 on linux (ubuntu 24)

MMM.fzz (449.4 KB)

2

Adding a screenshot. here one sees two traces selected. It’s not possible to select section one or two. You only get both. This is not good.

2traces
2traces405×550 107 KB

EDIT: after checking 1.0.4 and 1.0.3 the behaviour occured in both.

On the third try I managed to get it. First removing both traces. Then from header to 3.3k. Place trace in the background. Then place next trace from 3.3k to the other 3.3k (bottom) which automatically went top. fine. Why are traces sometimes treated as a whole? It’s a right pita.

3

Yep appears to be a bug. It was introduced between 1.0.3 and 1.0.4 it appears. 1.0.3 reacts as expected the trace stops at the first connection when moved from top to bottom.

capture1
capture11118×826 252 KB

in 1.0.4 and later it changes the entire trace which looks to be incorrect..

capture2
capture21124×825 265 KB

You need to open an issue on github here:

Going back to 1.0.3 should work around the problem til it gets fixed I expect.

Peter

1 Like
4

Ok, thanks for pointing this out. I’ll try in 1.0.3 again, though i thought it happened there too. It’s a bit annoying since my open projects get wiped every time i switch.

I’ll post an issue.