Thanks for the reply @microMerlin.
I was running on Windows 10 - I’ve since moved my project over to my Linux box.
0.9.3b was the latest version I could find on the internet that I could download without making a contribution. I love to contribute to good projects, but this was my first introduction to Fritzing and so I wanted to “kick the tires” so to speak before committing cash.
As it happens, I love Fritzing - in spite of the bugs. I’m 35 year veteran software engineer with open source experience, so I can always pull the source and fix issues if I want to put the time into it. So I went to the official site and paid to download the latest.
After upgrading, I didn’t see any more net label issues, but that is perhaps because I manually fixed them all before loading my project into the latest version. Fixing the problem involved deleting all the nets with issues and recreating them manually - there were a half dozen - it was not hard.
Creating a small sample with the problem is difficult because I don’t know what I did to cause it. I didn’t do anything particularly strange, but one thing may have contributed to the cause - I discovered ctrl-d (duplicate), which is an incredible time saver. Of course, this creates ports with the same net label as the source object, so there’s a good chance of creating an object that has some connection with the source object.
The problem doesn’t show up in the schematic view. I discovered it when I moved over to the PCB view to create my board and found several nets were interconnected (It was strange to see a microcontroller with all the digital pins tied together!)
I started writing an EDA program very similar to Fritzing (before I discovered it) last year after playing with the free stuff that was out there - i.e., KiCAD, etc. Most software was clearly written by people the really understood EDA, but didn’t have much experience designing software. My program was even using QT. I got as far as the canvas and a few parts, but gave up when I realized how much time it was going to take. Needless to say, i was thrilled to discover Fritzing - and that it was open source!
Regards,
John