Project

General

Profile

Bug #9953

Lighttable uses wrong image when mouse is not on the image.

Added by Kees Guequierre about 6 years ago. Updated over 5 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
05/11/2014
Due date:
% Done:

0%

Estimated time:
Affected Version:
git development version
System:
other GNU/Linux
bitness:
64-bit
hardware architecture:
amd64/x86

Description

17:46 < andabata> when in lighttable, move your mouse to the right panel.. change image with pageup/pagedown. and hit one of the image rotation buttons..
17:46 < andabata> it will rotate the previous selected image. not the current one

Bug 9941 might be related to this aswell


Related issues

Related to darktable - Bug #9941: Zoom view (press z in lighttable) shows wrong file informationIncomplete05/04/2014

History

#1 Updated by Roman Lebedev about 6 years ago

  • Related to Bug #9941: Zoom view (press z in lighttable) shows wrong file information added

#2 Updated by Fernando R over 5 years ago

I was trying to reproduce it... and I know I think what's going on:

First of all, while in lighttable, "pageup" and "pagedown" scrolls the panel where all pictures are contained, but the selected picture remains the same (I guess this is the expected behaviour and not a bug).

Anyway, the thing is that when (in lighttable) you zoom in big enough so that only one picture is available, then, when you press "pageup"/"pagedown", it looks like you are changing picture while, in reality, you are, once again, just "scrolling".

Under these circumnstances, if you try to "rotate" the image (or do any other image operation), the effect will always be applied on the selected picture, which might not be the only one being displayed right now.

The only "fix" I can think of to avoid this "user confussion" is to make it more visually obvious which image is the active one (right now it is just a slightly different tone of grey).

What do you think?

PS: If this is what happened to "andabata", then it has nothing to do with Bug #9941

Also available in: Atom PDF

Go to top