Version: 0.8.0 (using KDE 4.8.0) OS: Linux Steps to reproduce: 1.) In Browse mode, click on image so it fills view window 2.) Click and attempt to drag that image to sidebar with folders showing 3.) When the drag hits the folder list, the mouse cursor will disappear and appear at the right edge of the screen, moving to the left. This is weird, and a bug. All I wanted to do was drag and drop an image to a folder to move it. Reproducible: Always Steps to Reproduce: Steps to reproduce: 1.) In Browse mode, click on image so it fills view window 2.) Click and attempt to drag that image to sidebar with folders showing 3.) When the drag hits the folder list, the mouse cursor will disappear and appear at the right edge of the screen, moving to the left. Actual Results: Steps to reproduce: 1.) In Browse mode, click on image so it fills view window 2.) Click and attempt to drag that image to sidebar with folders showing 3.) When the drag hits the folder list, the mouse cursor will disappear and appear at the right edge of the screen, moving to the left. Expected Results: Image would be deposited in folder dragged to. OS: Linux (x86_64) release 3.2.2 Compiler: gcc
I think that the correct behavior should be this: 1) if image is enlarged, drag function is pan 2) if image is smaller than window, drag function is drag & drop
*** Bug 311890 has been marked as a duplicate of this bug. ***
Git commit bfac8b3731b27dcb45a8542c990251935960c7d4 by Benjamin Löwe. Committed on 28/12/2012 at 16:37. Pushed by bennihill into branch 'image-panning-improvements'. Improved panning of zoomed images: - Panning in images is faster now - When panning, the mouse pointer becomes invisible. After panning it reappears at the position where panning started. - Don't switch to panning mode when whole image is visible. Instead the image could be dragged and dropped somewhere (not implemented yet). See review request for remaining issues. REVIEW: 107985 M +25 -32 lib/documentview/abstractimageview.cpp http://commits.kde.org/gwenview/bfac8b3731b27dcb45a8542c990251935960c7d4
Will be fixed in 4.11.0.