Skip to content
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

Open
766F6964 opened this issue May 17, 2021 · 3 comments
Open

Move to next page using arrow keys #17

766F6964 opened this issue May 17, 2021 · 3 comments

Comments

@766F6964
Copy link

766F6964 commented May 17, 2021

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 or p.

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:
navigation

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:

  • Switch pages with n or p (fast navigation through images, to quickly find one)
  • Automatic page switching with arrow keys (slow navigation, when actually looking at the images)

I hope you don't mind all these suggestion issues ;)

@ckardaris
Copy link
Owner

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.

I hope you don't mind all these suggestion issues ;)

Keep them coming. I am really eager to find out about other people's experiences with ucollage

@766F6964
Copy link
Author

It is a very "violent" change of the view, caused by a simple key press that behaves differently in all the other cases.

It's not entirely consistent, the way I see it. Right now, it is for example also not possible to go to the next/previous image when opened with enter using the arrow keys (only with n and p). Arrow keys is the common way to go through pictures in other image viewers. If arrow-keys works to go through the next/previous image in grid view, they should behave the same in fullscreen/view-mode.

Anyway, I would like to discuss this further, because it's totally doable. Maybe some other people express their opinion on this.

Maybe make it optional? For example a flag/environment variable that could be set to 0 or 1, to allow for this behaviour?
Another idea, if you are not a fan of directly switching to the next page, could be going to the next row, and only go to the next page when we at the bottom right image.
nav2

Again, all of these don't have to be the default behavior, but it would be nice to have to choice to enable such behavior.

@ckardaris
Copy link
Owner

Another idea, if you are not a fan of directly switching to the next page, could be going to the next row, and only go to the next page when we at the bottom right image.

There is a default keybinding with Space and the corresponding function call _select right (see [1]) to wrap to the next line. But again the next batch is not fetched after reaching the right bottom image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants