After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 693208 - Method to copy layer between images could use improvement
Method to copy layer between images could use improvement
Status: RESOLVED DUPLICATE of bug 637313
Product: GIMP
Classification: Other
Component: User Interface
2.8.2
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-02-05 15:36 UTC by Pierre Ossman
Modified: 2013-02-06 01:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pierre Ossman 2013-02-05 15:36:54 UTC
Trying to copy a layer between to images is right now unfortunately fairly difficult to do (at least the only way I managed to find). It would be nice if this could be improved so that it was obvious how to do it. :)

If you're in single window mode, the method I found is:

 1. Make the TARGET image active.

 2. Undock the layers toolbox so it is free floating.

 3. Enable "Show Image Selection" on the new layers window.

 4. Switch to the SOURCE image in the combo box that has appeared.

 5. Drag layers onto the TARGET image.

This took my a fair bit of googling and guesswork to discover.

The methods I expected to work (and tried first):

 a) Simple copy/paste. This just copied the contents of the layer, e.g. turning a text layer into a simple rasterised version.

 b) Dragging the layer from the SOURCE image, hover over the TARGET image tab to switch, then dropping it over the TARGET image. This made the cursor switch properly, but had no effect. Maybe the switching of active image breaks the state of the ongoing drag-and-drop.
Comment 1 Michael Schumacher 2013-02-06 01:40:05 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 637313 ***