swapping breadboards crashes fritzing

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

Please use labels and text to provide additional information.

Original issue reported on code.google.com by jenn...@gmail.com on 23 Jan 2009 at 4:53

[GoogleCodeExporter]

They should also be made swappable

Original comment by jenn...@gmail.com on 23 Jan 2009 at 4:55

[GoogleCodeExporter]

half breadboard and full breadboard are swappable, but even without putting
components on the boards, swapping causes the application to crash

Original comment by jenn...@gmail.com on 28 Jan 2009 at 12:55

• Changed title: swapping breadboards crashes fritzing

[GoogleCodeExporter]

got this bug to replicate, found the point where it crashes, and why, but 
waiting
till jonathan is back, in order to help me fixing it :)

Original comment by meru...@gmail.com on 28 Jan 2009 at 1:01

[GoogleCodeExporter]

fixed the immediate cause of the bug in r2283 (which was that the old bus data
structure wasn't being cleared during the swap), but since this is the first 
time
we've tried swapping parts with buses, I'm leaving the bug open for other 
possible
lurking crashes.

Original comment by irasc...@gmail.com on 28 Jan 2009 at 2:46

[GoogleCodeExporter]

PS.  I wouldn't have made these parts swappable, or at least not swappable once
something is connected to them, because it's just asking for trouble.

For example: drop an LED onto the right half of the big breadboard, then swap.  
The
LED is now disconnected, which is reasonable.  Now undo the swap.  The LED is no
longer connected.

For a better example, wire up several parts on the right half of the big 
breadboard,
and then autoroute.  Now do a swap to the half breadboard.  Most everything is
disconnected.  Now go to pcb view.

Original comment by irasc...@gmail.com on 28 Jan 2009 at 2:54

[GoogleCodeExporter]

Different sized breadboards are indeed strange components to swap, but if 
they're not
swappable, the question then becomes what's the best way to show the user that 
there
is more than one breadboard type.  For example, if i chose a red LED component, 
i'm
offered information that there are other colors available.  But with the 
current bin,
 if breadboards are not swappable, then the user won't know that there are other
breadboards available.  And while they are both available from the all parts 
bin,
they have the same icon in the component bin, because reducing the size of the 
icon
makes it difficult to tell that the icon is representing a breadboard.

Overall, i would say breadboard swapping should be very low priority, but it's
somthing to think about

Original comment by jenn...@gmail.com on 28 Jan 2009 at 3:11

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

[GoogleCodeExporter]

Perhaps we should constraint parts with buses from being swappable, or at least 
after
something is connected to them.
Otherwise, how can we prevent a user from creating a breadboard and placing it 
into
the "breadboard" family? That's all she needs to make it swappable (so far)

And here's a weird case, but if she makes a breadboard with exactly the same
connectors and buses, but with a different, for example, color? shouldn't it be
swappable no matter if something is connected to it or not?

Original comment by meru...@gmail.com on 28 Jan 2009 at 3:28

[GoogleCodeExporter]

r2283

Original comment by irasc...@gmail.com on 31 Jan 2009 at 10:55

• Changed state: Fixed