when your image is bigger then the real screen size (or you simply zoom in) there is an option to click and hold the picture, move it around with your mouse. Now with the latest gwenview its not possible anymore. the mouse will stuck in one point and only jumps wild around without much movement to the picture. that funktion is broken for me Reproducible: Always Steps to Reproduce: 1. open a picture 2. zoom in to make it bigger then the actual screensize 3. try to drag it around with your mouse Actual Results: the mouse jumps around and the picture doesnt move Expected Results: it should move the picture smooth around with your mouse i'll choose Severity: "Major" because when gwenview is an imageviewer and you cant move images in a zoomes state to view them, its true that "A major feature is broken"
Created attachment 91389 [details] screencast
I am also affected on my 2 computers by this bug, using Gwenview 5.0.0 pre (KDE Frameworks 5.7.0). Gwenview came pre-compiled from the Manjaro repos.
It also affects me... I found out, though that if dragged VERY slowly, the image wil pan... But if you pan normally the weirdness starts...
At least for me, with the today's Arch update to KDE Apps 15.04 this problem was solved... Can others confirm as well? Thanks :)
Glad to see that this bug has been reported, I thought it was just my computer. Problem is still occurring for me on Gwenview 5.0.0pre, on Kubuntu with all upgrades through 4/27/2015.
Appears to be fixed in 15.04 I'm using Gentoo kde-apps/gwenview from kde-libs overlay 15.04.0
Appears to be fixed here as well.
Gwenview Version 5.0.0 pre KDE Frameworks 5.9.0 Another video of this problem: https://drive.google.com/open?id=0B0Golainx_WBYWFwM1pUVlJ2NDA&authuser=0
Although the mouse can no longer quit the screen to appear elsewhere (continuous scrolling) in Gwenview 5.0.0, the bug seems to be gone in that version.
Multiple confirmations, changing status.
...can you please tell me when was this fixed? I still experience this in 5.0.0 pre of kubuntu 15.04
*** Bug 347159 has been marked as a duplicate of this bug. ***