When playing a slideshow, if I use the keyboard to see the previous/next image it will stop the slideshow. is there a way to keep playing the slideshow?
The slideshow should only stop if you go to the previous image, not to the next. It would be logical to assume that if you want to go backwards the slideshow should stop. But then you can press CTRL+R to resume the Slideshow. The default resume hotkey can be changed in KeyMap.txt (IDM_SLIDESHOW_RESUME). I would recommend to use ENTER/RETURN for easy access.
Last edit: Melvin Nava 2021-03-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wonder if JPEGView is still in development. I was willing to design a multires icon for the next version of it but I guess it is no longer being mantained since last update was 3 years ago.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Leandro I'll incorporate a multires icon into my fork if you come up with one. Preferably the same icon JPEGView's been using for years, one we know and love though
You can post it on my GitHub fork so I can incorporate it easily from there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The slideshow should only stop if you go to the previous image, not to the next. It would be logical to assume that if you want to go backwards the slideshow should stop. But then you can press CTRL+R to resume the Slideshow. The default resume hotkey can be changed in KeyMap.txt (IDM_SLIDESHOW_RESUME). I would recommend to use ENTER/RETURN for easy access.
Last edit: Melvin Nava 2021-03-12
Hmm I see. Thanks for that tip.
I wonder if JPEGView is still in development. I was willing to design a multires icon for the next version of it but I guess it is no longer being mantained since last update was 3 years ago.
@Leandro I'll incorporate a multires icon into my fork if you come up with one. Preferably the same icon JPEGView's been using for years, one we know and love though
You can post it on my GitHub fork so I can incorporate it easily from there.