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
DPI-aware thumbnails #211
Comments
Hi @feidaman v4.0 fully supports high DPI up to 500%, so you will see no alignment and blur issues when using the app. There are a few options to change thumbnail size in Settings dialog, but according to your feedback, the largest 128px size seems still very tiny in your resolution. I will add some more size options (such as 256px, 512px, ...) for a better UI. Thanks |
Thanks :) The GUI itself definitely supports high DPI, for example the toolbar buttons look look glorious. But it seems the thumbnail size is measured in actual pixels. I suspect the 32-pixel setting would be usable on a low DPI display, while on something like the Surface Pro 4 it would be too small. Here's what the 32-pixel setting looks like on my screen: Are the thumbnails supposed to look smaller than the toolbar buttons? At the moment I don't have a low DPI display to test with because I'm in the middle of moving home and my desktop PC is packed away. |
Thanks for the screen shot. |
Added new options for thumbnail: You can set a customized value in Windows Registry: |
Thank you |
On my Surface Pro 4, which has very high DPI, even after setting thumbnail size to 128 pixel, thumbnails still look quite small, and 32-pixel thumbnails are way too small to be useful. This makes me think the program currently is not DPI-aware (but I could be wrong!). Making it DPI-aware would have an additional benefit: the thumbnails would look roughly the same size on any system, which is especially useful when using the program in portable mode.
If the program is already DPI-aware, please forgive me. In that case it would be useful to add an extra 256-pixel option.
Thank you!
The text was updated successfully, but these errors were encountered: