The decimal separator around here is the comma.
I don’t get a messy picture, though. Nothing at all comes in - command line echo:
Successfully read file "C:\Temp\1-original.svg"
No objects added to selection.
Drag a window to zoom ( All Dynamic Extents Factor In Out Selected Target 1To1 ): _All
Choose option ( Extents Selected 1To1 ): _Extents
Unable to zoom some views - no objects are visible.
And this is in the May 2nd release…
OK… I’ve played with this a lot more now.
I tried importing the same SVG file again in the same session and got this message:
A block definition named "path-1" already exists.
I guess it’s unexpected behavior that an import would create a block at all - but in the end, I suppose, this is correct in this case…
I then went into the Block Manager and did a block count on that instance and got this:
Block Name, Top Level, Nested, Total
path-1, 0, 0, 0
Grasping at straws I then exported that block to the CSV format and opened that file to read the following:
"Object Count","Layer Name","Object Name","Object Category","Object Type","Attribute Keys","Attribute Texts","Object Keys","Object Texts"
The first layer in my template is the
ClippingPlanes layer. It is turned off.
Turning on this layer shows the SVG geometry successfully imported.
I guess I was lucky there was a < defs > element in that original SVG file or I would never have found the contents.
Would you agree with me that importing a SVG file into a hidden layer is a bug? In my mind, it would have to come in on the active layer…