Copy and past over different documents with clones

Bug #169120 reported by Dino4k
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Confirmed
Medium
Unassigned

Bug Description

Hi there,

if you try to copy and past a clone of an actual object into another file
you just past nothing which leads to confusion. I'm not sure what the best
solution would be. Perhaps always copy the actual object/data and not the
clone - since its just a consistent appearenace to the user.

At least if you past into another file and its obvious to inkscape that it
cannot past the clone since the reference is missing warn the user about it
so he know why it is not working.

thanks.

Revision history for this message
Ryan Lerch (ryanlerch) wrote :

When you try to paste a clone in a new document, the status bar reads "Orphaned Clone in layer n press shift + D to look up original." and when shift D is pressed - "Cannot find the object."
IMO this is enough feed back for this... a popup dialog would be to intrusive.

Changed in inkscape:
importance: Undecided → Low
status: New → Invalid
Revision history for this message
jimmac (jimmac) wrote :

I think a much better behavior when pasting a clone into a new document without a parent in the clipboard is to unlink from parent and paste the actual object.

Changed in inkscape:
status: Invalid → New
Revision history for this message
Guillermo Espertino (Gez) (gespertino-gmail) wrote :

I second the jimmac's idea. That's elegant, it's not obstrusive and is already supported as one of the possible alternatives when the original is removed, so I guess a routine for that is already coded.

Changed in inkscape:
status: New → Confirmed
Revision history for this message
chucky (tomas-mikula) wrote :

I have a problem similar to this:
When both the original and the clone are pasted together and an object with the same id as the original already exists in the document, the original is renamed, but the clone still links to the same id, i.e. to the wrong object.

Revision history for this message
Philippe Joyez (ubuntu-5-pjoyez) wrote :

Hi

I'm really a beginner with Inskape, and I ran into this problem when copying a large group containing clones at 3rd or fourth level. In the case I'm referring to, the group resulted from a pdf import and the clones were just characters, with the original being invisible in <defs>, as I learned afterwards.

As described above, when pasting in another drawing, all the clones are missing (so that all the text is gone), but the status bar says "group of N objects" (the number being that of the original). At first I had no clue of what was going wrong in this process and thought Inkscape was so buggy that it was not even able copy from one of it's own drawing to another.

I think it's important to fix this annoying problem which may turn inexperienced users away from Inkscape. At the very least the warning in the status bar regarding orphaned clones should appear whatever the depth of the clones in the pasted elements.
One way to provide a real fix is like Jimmac suggested : the paste operation could unlink a parent which is not in the clipboard. Other ways are possible: one could copy the parent in <defs> of the destination drawing, which seems the good thing to do for the case I ran into.

su_v (suv-lp)
tags: added: clipboard clones
removed: other
Revision history for this message
su_v (suv-lp) wrote :

Raising to the same Importance as possibly duplicate or at least related bug #220521 “Group element in <defs> section lost during copy/paste between inkscape windows”.

Changed in inkscape:
importance: Low → Medium
Revision history for this message
OC (olivier-c) wrote :

This looks like a duplicate of bug #167907 to me.

Revision history for this message
Shriramana Sharma (jamadagni) wrote :

I agree with Philippe that this bug would seriously impact usability of Inkscape and possibly alienate new users, and hence request that this be fixed soon.

I agree with jimmac on the methodology to fix this bug. If a clone is being copy-pasted, it should be unlinked from its original, but see below.

@chucky (tomas-mikula): I think you should report that as a separate bug. The bug here is for when only the clone is copy-pasted.

Anyhow, the combination of your bug and this one means that when copy-pasting a set of objects where one is a clone, Inkscape should check to see whether the original of the clone is also being copy pasted.

1) If no, then Inkscape should unlink the clone and paste it.
2) If yes, then it should check to see whether an object with same ID as the original is already present.
2a) If yes, then it should rename the original being pasted and re-point the clone to the new ID.
2b) If no, then it should just paste the original and clone as is.

Note that when a set of objects is being copy-pasted, and one of them is a clone, it is not guaranteed that the original of the clone is also in the set of objects, hence the above checking procedure is required.

Revision history for this message
Shriramana Sharma (jamadagni) wrote :

I think chucky's bug is already reported as bug 165936... Anyhow, I have marked this as a dup of bug 167907. I will copy-paste part of my last comment there.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.