Creating a second set of tiled clones deletes the first set? Is that deliberate? It doesn't seem like a useful "feature" to me. I wanted to make two sets of tiled clones from one parent.

Stumbled about that, too, and don't know if it's intended or not. The issue is probably with the 'Remove' button and what it will remove exactly ('remove last' and 'remove all' could be options...)

All this time I've been using the remove button....

If you want to workaround, you can clone one of the original clones and use different tile settings - updating the original parent will update all.

I see this too, 0.92.2, 64-bit 7z package, Windows 7 Pro 64-bit.

Has anyone researched this? I mean, if the 2nd click removes the results of the first click, what is the Remove button for? It would seem to be inappropriate behavior.

Although having taken some time to test, it seems to be happening as far back as 0.47. Didn't test any further back than that.

I didn't find any bug reports, which would seem to indicate it's not a bug (or would be reported by now, surely).

But I'm curious enough that I'll probably post to the user mailing list, just to find out. I'll post if I get any replies.

Subsequent testing reveals that the first array is deleted whenever the same parent is used to make another array - not just when the 2nd array immediately follows the first. Now I''ve made a few arrays with a few different parent objects, after the first array with the first object. When I go back and select the first object, and try to create a new array, the first array is replaced by the 2nd.

Here's the archive link for the message I sent to the mailing list, in case someone wants to follow it, without subscribing to the list. https://sourceforge.net/p/inkscape/mail ... /36068041/