-
Notifications
You must be signed in to change notification settings - Fork 3
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to next page using arrow keys #17
Comments
This is something I had thought about when I was writing the image selection code. It seems to me that the action of fetching the next batch of images is not what the user would expect when reaching the edge of the grid. It is a very "violent" change of the view, caused by a simple key press that behaves differently in all the other cases. Anyway, I would like to discuss this further, because it's totally doable. Maybe some other people express their opinion on this.
Keep them coming. I am really eager to find out about other people's experiences with |
There is a default keybinding with |
An idea for a quality of life improvement:
Currently the user is able to use arrow keys to navigate between the pictures currently shown in the grid.
The user can also switch to the previous/next page using
n
orp
.Intuitively, I think it would make sense to automatically switch to the next/previous page, when navigating past the borders of the current page, while remaining in the same row from the previous page.
Example:
When the user is at the rightmost image on the left page, the right-arrow key should switch to leftmost image on the next page, while remaining in the same row as the previous page (In this example, the middle row).
Obviously, the same logic should apply when switching to the previous page.
In my opinion, its good to have both options available:
n
orp
(fast navigation through images, to quickly find one)I hope you don't mind all these suggestion issues ;)
The text was updated successfully, but these errors were encountered: