Next/Previous picture keys should be active also in Lighttable mode
In Darkroom mode, [Space] switches to the next picture, [Backspace] to the previous picture, it would be very nice if these keys were to do the same in Lighttable mode.
I often view my images sequentially (e.g. for rating/tagging/culling) and have not found a convenient way of switching to the next image.
If I could just - for example - rate an image (one of the keys 123450r) and then switch to the next one with one keypress, that would be wonderful, but I have not been able to find the key that does that.
#1 Updated by Richard Wonka almost 6 years ago
In fact, I find the [Space]/[Backspace] combination not very intuitive, [backspace] usually deletes things - I only every tried pressing this key because I had read about it doing something different and unexpected.
[PgUp]/[PgDn] seem to make more sense, after all, that is what they were put on the keyboard for.
In lighttable they could shift the lighttable or file manager up/down one page at the current zoom level, resulting in a sequential view when zoomed in to one picture.
Whatever the keys are, though, they should definitely remain the same throughout the application. Consistency is king for usability.
#2 Updated by Simon Spannagel almost 6 years ago
In lighttable the arrow keys should do that job (they do for me).
Pressing ALT+1 to get only one image displayed, pressing TAB to hide all panels and the using arrow keys l/r to switch.
But you are right with consistency - I'm considering putting this into 1.0.1, really makes sense in terms of consistent UI.
#5 Updated by Tobias Ellinghaus over 5 years ago
- % Done changed from 0 to 100
- Target version changed from Candidate for next patch release to Future
- Status changed from New to Fixed
There are a few issues in here. Losing focus of the lighttable is fixed and you can change the keys used in the preferences. At least in theory. At least for me the arrow keys don't work in darkroom, I guess they are grabbed before they can do what they should. Since this ticket is quite old and we don't like catch-all reports I am closing this as Fixed. Feel free to open single tickets for single issues that are still present.