search

buixuanan / fritzing

Automatically exported from code.google.com/p/fritzing
0 stars 0 forks source link

SVG export skips image for custom part. PDF/PNG export are OK #2835

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Load mosfet_not_final.fzz (attached)
2. View breadboard
3. File -> Export -> As Image -> SVG, pick filename, OK
4. View resultant SVG in an SVG viewer. I tried Inkscape, Firefox, Chrome, 
GIMP, ...

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

Most of the breadboard appears in the SVG fine, but the button is missing. If I 
export to PNG or PDF, the button appears as expected.

The SVG I used for "load image for (breadboard) view" is attached as 'Button 
0.2" x 0.2." breadboard.svg'

What version of Fritzing are you using? On what operating system?

Fritzing git commit 18564b3 "more updated examples" (the packaged version on 
Ubuntu crashes)
Linux Ubuntu 12.10.

Original issue reported on code.google.com by stephen....@gmail.com on 20 Dec 2013 at 6:29

Attachments:

GoogleCodeExporter commented 9 years ago 
Not sure why this part is being excluded. Further investigation required.

Original comment by irasc...@gmail.com on 21 Dec 2013 at 7:55

GoogleCodeExporter commented 9 years ago 
In the svg attached in the issue report, the following structure exists:

            <g gorn="0.3.0.0.0"  id="g3081" partID="77470">
                <g gorn="0.3.0.0.0"  id="breadboard">
                    <g gorn="0.3.0.0.0.0"  id="g3084">
                        <g  transform="matrix(1,0,0,0.35103403,0,15.889714)">

However, in the svg saved with the .fzz file, one element is gone:

                <g gorn="0.3.0.0.0"  id="g3081" partID="77470">
                    <g gorn="0.3.0.0.0.0"  id="g3084">
                        <g  transform="matrix(1,0,0,0.35103403,0,15.889714)">

And since the "breadboard" id is missing, the part does not appear in the 
exported svg.

The question is, at what point did that element get removed?

Original comment by irasc...@gmail.com on 21 Dec 2013 at 5:26

GoogleCodeExporter commented 9 years ago 
Oops. This may be user error; I may have screwed up when attempting to do the 
following steps, and not actually ended up using the latest SVG For the button 
in my circuit. I tried to:

a) Export the existing button image
b) Edit it in Inkscape to resize it etc. As part of this, I had to ungroup some 
components of the image to move them around. I think this lost the 
id=breadboard XML tag.
c) Re-import it
d) I noticed that the image didn't export from the breadboard view
e) I manually edited the button image SVG to add the id=breadboard XML tag, 
since I noticed this was missing relative to some other working images
f) I re-imported the updated image (or at least I thought I did).

I think I screwed up step (f), and ended up not re-importing the image (or 
perhaps not replacing the component in the breadboard with the updated button, 
and hence not pulling in the newly imported image).

Anyway, I re-imported the image and swapped the component out in the 
breadboard, and it exports OK now.

I guess I should just close this bug?

Original comment by stephen....@gmail.com on 24 Dec 2013 at 3:30

GoogleCodeExporter commented 9 years ago 
Or perhaps there was confusion between the "Temp" and "My parts" component 
libraries.

Original comment by stephen....@gmail.com on 24 Dec 2013 at 3:52

GoogleCodeExporter commented 9 years ago 
The parts files exist in multiple places, in the user local storage (where the 
parts editor saves it) as well as in one or more sketch files. Fritzing would 
load the part from the local storage first, so that would be the "master" 
version. But if you load one of the sketches with that part, since it already 
exists locally, it probably should not appear in the Temp bin. So this sounds 
like a bug, even if the original issue was not a Fritzing problem.

Original comment by irasc...@gmail.com on 24 Dec 2013 at 8:37

GoogleCodeExporter commented 9 years ago 
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:42