I have created an SVG within Inkscape for a template box/sleeve for packaging. When I then upload my design into the cutting software (Cricut Design Space), it has added a rogue path. This path cannot be seen when viewing the project in explorer.
It has done this following my 'combine' Ctrl+K to attach the perforations (dashed paths) to the main object. I need them to be combined though!
I am experiencing this issue with almost every project I work on.
How do I remove this unwanted path if I cannot see it in Inkscape?
NB: I'm fairly new to all this, so i'm sure it's something i'm doing wrong. Any advice would be so greatly received!
@Polygon Thank you. I'm still discovering all of the features and options so I will check this out to see if it reveals anything.
For this particular design, I went back and redrew the dashed lines and ensured that they snapped to the outer nodes. It seems that by doing that and combining one at a time, it sorted it. It'll no doubt come up again on my next one - it always does!
Beyond the Basics Unwanted paths
Inkscape.org
I have created an SVG within Inkscape for a template box/sleeve for packaging.
When I then upload my design into the cutting software (Cricut Design Space), it has added a rogue path.
This path cannot be seen when viewing the project in explorer.
It has done this following my 'combine' Ctrl+K to attach the perforations (dashed paths) to the main object.
I need them to be combined though!
I am experiencing this issue with almost every project I work on.
How do I remove this unwanted path if I cannot see it in Inkscape?
NB: I'm fairly new to all this, so i'm sure it's something i'm doing wrong. Any advice would be so greatly received!
Many thanks, Charlie
v6.17.143 ~ Windows 10
In Inkscape go View->Display Mode->Outline and check for any unwanted strokes perhaps.
@Polygon
Thank you. I'm still discovering all of the features and options so I will check this out to see if it reveals anything.
For this particular design, I went back and redrew the dashed lines and ensured that they snapped to the outer nodes. It seems that by doing that and combining one at a time, it sorted it.
It'll no doubt come up again on my next one - it always does!
Many thanks, Charlie