Page 1 of 1

0.84: Move tool doesn't move promptly

Posted: Mon Feb 20, 2017 9:31 pm
by helmut
XnView: MP 0.84
OS: Windows 10 - 64bit

When using the move tool (hand cursor) to move a zoomed-in image and moving it more than possible (in any direction), it doesn't move back right away.

Effect: Irritating user interface

To reproduce:
1. Open an image in Viewer
2. Zoom into the image so that you can see scrollbars.
3. Right-Click onto the image and keep the mouse button pressed.
XnView displays the hand cursor indicating that moving is active. (correct)
4. Move the image to the very top and even more than that (you can't, but do it ;) )
5. Move the image back towards the bottom.
Actual behaviour (bug): You will notice that the image doesn't react to your moving at first. :bug:

Expected behaviour: Moving should be as prompt as possible - even when moving the image beyond its borders.

Re: 0.84: Move tool doesn't move promptly

Posted: Mon Feb 20, 2017 11:49 pm
by vertigo
Reproduced. It's keeping the hand cursor on the same point in the image. Not sure if this is intentional or just happens to be how it works (i.e. the cause or the effect). If the image started moving in the new direction immediately, the hand cursor would be in a different spot. There's no reason to do this, and if, for example, you go up until it the picture stops going up, then go left or right, then come back down, the cursor will be in the same vertical location on the image but the horizontal location will have changed (and, of course, this doesn't matter).

Re: 0.84: Move tool doesn't move promptly

Posted: Tue Feb 21, 2017 4:09 pm
by helmut
Thank you for reproducing my problem and your additional info, vertigo.

I'm not quite sure but I think it's a bug. Before moving this into the "bug pipeline" I'll wait a bit to see what other users think.

Re: 0.84: Move tool doesn't move promptly

Posted: Thu Feb 23, 2017 1:45 am
by XnTriq
Reproduced. It's a bug, IMO.

Re: 0.84: Move tool doesn't move promptly

Posted: Thu Feb 23, 2017 8:42 am
by helmut
XnTriq wrote:Reproduced. It's a bug, IMO.
Thanks for checking and your feedback, XnTriq.

Note: I've tried in XnView Classic v2.39 and the problem occurs too. Until now, noone else complained so this can be dealt with low priority or even postponed if it turns out to be a difficult fix.

:arrow: Reproduced