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 682591 - Single Window Mode - Can't drag+drop layer to another image
Single Window Mode - Can't drag+drop layer to another image
Status: RESOLVED DUPLICATE of bug 676522
Product: GIMP
Classification: Other
Component: User Interface
2.8.2
Other All
: Normal minor
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-08-24 08:44 UTC by Alec_Burgess
Modified: 2012-08-24 08:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alec_Burgess 2012-08-24 08:44:44 UTC 
Using Jernej Simončič 2.8.2 build of 2012-Aug-23 (on 32-bit system)
(1) In non-Single-Window-Mode with two or more images open I can drag a layer (from the layer dialog) to the window containing another image and drop the layer on it. A copy of the original layer is added to that image.

(2) Attempting the same thing in Single-Window-Mode: 
(a) drag the layer from the layer dialog to the thumbnail of another image and drop: nothing happens.
(b) as above but hover long enough that the other thumbnail opens as the selected image in the single window and drop the layer on the window: nothing happens.

Workaround - switch to Single-Window-Mode and do as in (1) above.

FWIW: I recall discussion in DEV forum of this and I think the answer proposed was that 2b above should work. I had been using 2.8.1 Partha-portable build at the time of that discussion (I think) and could not get it to work. AFAICT there is not another bug covering this and its not covered in the 2.8.0 --> 2.8.2 release notes.
Comment 1 Michael Natterer 2012-08-24 08:54:16 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.

(I know that other bug sounds a bit different, but it is the same issue).

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