-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
[FR] horizontal gallery improvements : display uncropped images ? #53
Comments
For thumbnail generation, I have two methods. One that is multi threaded/asynchronous and more resource intensive, but it only fires if the amount of images is at or above 250. What you are seeing is a background single threaded use. I have uploaded a new test version to Sourceforge, where the condition is set to 40 images instead of 250. Tell me if that works better for you. For the size and padding, let me think about it and get back to you on a later date. |
Alright, progress report. With release 1.6 I have improved the thumbnail gallery loading time. It should be a lot faster now, For resizing thumbnail dimensions, that will be a bigger project. It is something I want to accomplish. I'll start working on it after I've created my image resizing window. Edit: This will take place during Avalonia conversion #58. |
Is your feature request related to a problem? Please describe.
some suggestions for the horizontal gallery view:
add an option to display the horizontal gallery thumbnails with fixed height but adaptative width so that they are not cropped to square ratio, as in the example below:
additionnal setting for custom thumbnail height (slider ?)
additionnal adjustments for padding/margin between the images
also the thumbnail generation takes a very long time compared to other viewers in the current version (test folder containing 100 pics of 4860x3280 on a network folder, current picview takes about 600-700ms to display a thumbnail, see the gif below. xnview is about x10 times faster on first navigation without using thumbnail cache/indexing)
The text was updated successfully, but these errors were encountered: