Parts editor svg import on 1.0.1 is broken in at least this case.

[vanepp]

Current Behaviour

In this forum thread

https://forum.fritzing.org/t/cant-get-svg-to-work/20580/

someone tried to import this svg in to Fritzing 1.0.1 using the parts editor

while the svg has a number of issues, Fritzing 1.0.1 has a number of bugs compared to Fritzing 0.9.10. So lets start with this .fzpz file (remove the tailing .zip to keep github happy)

cd4051.fzpz.zip

which is the version of the part posted to the forum on Fritzing 0.9.10. Schematic currently looks like this:

so edit the part in the parts editor

then load the svg at the top of this post as the schematic svg. Due to a bad font definition in the svg we get the font swap message

clicking ok uploads the schematic svg correctly.

Now on to 1.0.1. First I created a fzpz with a blank schematic and loaded it in to Fritzing 0.9.10:

as the new svg was created in Illustrator and dimensioned in px I replaced that svg with a standard Inkscape formatted svg dimensioned in inches to avoid any Illustrator oddness in the following

cd4051-blank-schematic.fzpz.zip

here the schematic shows up blank as expected. Switching to 1.0.1 things change. While the schematic is blank, and I expected it to look like 0.9.10, it in fact loads a svg looking like the generic IC (which is the family name in the fzp file) which is unexpected.

now start parts editor which looks to load the svg for the generic IC (which is again different than 0.9.10)

now upload the new schematic svg but it doesn't load the input svg, but rather makes some odd connector changes (circled in red here.) with none of the changes in the original svg which is incorrect.

Build: Version 1.0.1 (rcCD-1654-0-8f5f1373 2023-09-06) 64 [Qt 6.4.3]

Operating System: Windows 10

Steps to reproduce:

see Current Behaviour

Expected Behaviour

I would expect 1.0.1 to load a blank svg as 0.9.10 did, instead it appears to substitute a svg based on the generic IC (which the family is)

When the new svg for schematic is loaded I would expect to see output as from 0.9.10 where the input svg is replaced in schematic rather than a corrupted copy of the original svg that appears.