CC - Item movement snapping to non-existent nodes

Software Carbide Create
1

I have a file with ‘phantom’ nodes. I have turned off ‘Snap to Grid’, and I’m moving objects by picking up at a node. In this mode, ‘snapping’ to other nodes is expected.

I’m getting snapping where there are no nodes. All my layers are visible, and selection in that area picks up nothing. Yet, the snapping persists.

I’ve marked the area with two red rectangles. Node snapping occurs between them.

image
image384×355 1.38 KB

Since I’ve already verified that it’s not because of something on another layer, I’ve hidden a couple that are just distractions.
test.c2d (3.8 MB)

2

It has something to do with the “Welsh Terrier” text — when it is moved the extra node repositions to match.

Not seeing anything when exporting it and opening it in Inkscape:

image
image2880×1728 239 KB

Exporting that as an SVG, deleting it, and reimporting it seems to have fixed it:

Welsh_Terrier_Club_v8.c2d (3.8 MB)

If we know how the file was made, and if it seems likely to occur often enough to trouble folks we can look into it further.

3

The original SVG that I see now creates the problem is here:
Welsh Terrier Club of America

This SVG was created in Inkscape, by importing an ‘.ai’ file (which is apparently some kind of PDF) and exporting as SVG. I used all default values for importing. Renamed as .pdf for uploading:
Welsh Terrier Club of America.pdf (1.1 MB)

I don’t know if this would be a bug in Inkscape (extra nodes created when not needed), or a bug in CC (should ignore these ‘phantom’ nodes).

4

The extra node that I found is associated with the letter ‘h’. Deleting that letter makes that node disappear as well. There are a ton of extra nodes above the text as well.

1 Like
5

As I’ve noted previously, I’d be a much less-grey, far less-stressed, and overall, much happier and younger individual if I could have back all the time and effort I’ve expended in my life fixing broken Adobe Illustrator files.

2 Likes
6

It looks like exporting the SVG from CC and immediately re-importing it removes all the phantom nodes. Given that, I would hope that the import process could just strip them on import instead.