Shoot. What I meant by close - was lower 48 states of US. I can’t ship to Canada - they won’t allow it - Customs will seize it. If you are ever in California for whatever reason - I would be more than happy to send you home with a half case of wine. I have friends in Toronto and they have managed to get a few cases over the border somehow…
Thanks again. I learned a lot from you guys, and solved a problem!
One cause of this is if the svg is dimensioned in px rather than mm or in. There are at least 3 svg dpi values (72dpi for old illustrator, 90 dpi for Inkscape < 0.9.2 I think, and 96dpi for Inkscape 0.9.3 and greater. Fritzing will try and guess at what dpi value is in use but often gets it wrong which changes the scale in Fritzing. I know how to fix this in Inkscape, but not any of the other svg editors.
Thanks I will look into this - I hadn’t edited an SVG before and assumed that if I imported a drawing into the editor it would preserve the key features (metadata) of that drawing…apparently not.
OK - I used Inkscape and it worked perfectly - thanks. I think Inkscape is a far better editor for SVG than the one I attempted to use originally. Either that or it is just more straightforward and I could see scale, units, etc without even looking for them…LOL.
In this particular case the editor is doing the correct thing, the problem is Fritzing is being helpful and trying to guess what the DPI setting should be and sometimes guesses wrong (especially after the 90DPI to 96DPI shift.) I don;t know of a way (although there may be one) to get Illustrator to use mm or in for the dimensions. I don’t use Illustrator and no one who does has shared a way to get it to use in or mm in place of px so far.
Inkscape certainly has its quirks and bugs but it is open source and therefore popular in Fritzing and once you learn them it works fairly well. The main thing to watch is that Inkscape font size output will end in px (i.e. font-size=“35px”) as that is what CSS calls for, and Fritzing wants font-size=“35” or else it will change the font size to 0 when parts editor is used. The python part checking script I wrote fixes this as it checks the part, but if you don’t want to use that, then replacing the “px” with blanks via a text editor is a good bet with Inkscape (and I expect most other editors as well since I expect they will all be CSS complient,)
You do not need a lot of advanced features of Inkscape to create and edit Fritzing part images. The “TinySVG” variant that Fritzing (mostly) supports does not handle gradients, masks, defines, and a lot of other things you can do in inkscape. To create connectors, you will need to learn a little about the Inkscape xml view, to add the connector id attributes. Or add them after saving from Inkscape.
Inkscape has options to save cleaner (from Fritzing perspective) images, but that can introduce its own problems. The rules about what works and doesn’t changes over time (Inkscape versions). Currently I am getting good results using Inkscape, file, Save As, Optimized SVG with output settings of:
Options
Convert CSS attributes to XML attributes
Collapse groups
Create groups for similar attributes
Work around renderer bugs
SVG Output
Remove metadata
Remove comments
Format output with line-breaks and indentation
Space, 2 characters
Strip the “xml:space” attribute from the root SVG element
IDs
Remove unused IDs
Preserve the following IDs: breadboard,schematic,copper0,copper1,silkscreen
Preserve IDs starting with: connect
No spaces in that list of ids. Those settings are remembered across sessions, so they only need to be set once.