Bug 233357 - Keyboard navigation in browse mode broken
Summary: Keyboard navigation in browse mode broken
Status: RESOLVED DUPLICATE of bug 258960
Alias: None
Product: gwenview
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-05 16:39 UTC by RalphB
Modified: 2017-06-19 13:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RalphB 2010-04-05 16:39:52 UTC
Version:           2.4.2 (using 4.4.2 (KDE 4.4.2), Kubuntu packages)
OS:                Linux (x86_64) release 2.6.32-19-generic

Most image viewers that I'm familiar with use either PageUp/PageDown and/or CursorUp/CursorDown to advance to the next or previous image when viewing images, in particular in fullscreen mode.

One can easily configure Gwenview to do the same.  Alas, this breaks browse mode, since I no longer can use the page or cursor keys to navigate the cursor in the browse window.  (Note that if the current folder contains a mixture of images and folders, the behavior of PageUp/Down is entirely unpredictable, as sometimes PageUp will behave as "move cursor multiple rows" and sometimes as "move cursor to next image".)

I strongly suggest to ignore certain key bindings in browse mode, including at least cursor keys, PageUp, PageDown, Pos1, End, and Return.  Alternatively, you might want to consider to use entirely separate keyboard shortcurts for each of the three Gwenview modes.

(I've found other bug reports and wishlists, e.g. #223291, that seem to share my general sentiment.)
Comment 1 Anirudh 2012-01-05 12:49:02 UTC
duplicate of Bug 258960 & Bug 131836.
Comment 2 Julian Steinmann 2017-06-06 17:49:51 UTC
Cannot reproduce with Gwenview 17.04.1.

When setting CursorUp/CursorDown as Next/Before shortcuts, you are still able to use browse mode normally.
Comment 3 Christoph Feck 2017-06-19 13:27:47 UTC
*** This bug has been marked as a duplicate of bug 258960 ***