-
Notifications
You must be signed in to change notification settings - Fork 123
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
"Original size" bug #374
Comments
Can you please demonstrate exactly the behavior you are looking for and how it has changed? Comparison pictures would be helpful. |
just set the system scaling to 150% or 200%, then open a picture and see what happens |
This was actually supposed to be intentional, but clearly I need to add an option. |
Interesting idea, but I've never seen any image viewer that scales images like qView does. If I have 4K display with 200 % scaling and I download 4K picture and view it fullscreen, I would expect it to be displayed in perfect 1:1 ratio. Since qView scales images, I assume it would blow picture to 8K and then downscale it to 4K and I would loose picture clarity since it would be presented basically in HD. So thank you for adding this to 5.0 milestone. |
Well the original bug report that led me to change it to this behavior argued that it is idiomatic on Mac. On mac, preview.app actually works this way. |
Hmm.. Never worked with Mac. Maybe it generates retina image @2... Anyway, I guess an option would be the best way to go to please everybody. |
I have the same issue on linux. other image viewer dont do this and correctly only use scaling for their UI element. this behavior caused me to incorrectly assume it was kde fault and report a false bug. |
There are two ways this could be expected to work:
There is no right way to do it, it's probably best to have a setting for it. Different programs handle it differently; image editors/viewers on Windows typically(?) do # 1, and web browsers do # 2. On macOS it usually only makes sense to do # 2 due to the way macOS handles display scaling - it's often rendering to a virtual desktop larger than the native resolution and scaling down; there's no guarantee that one pixel drawn will equal one pixel on the display. That said, the specific problem @shu307 was having goes further. If you notice, qView was making the 1920-wide image take up 100% of the display which matches neither of the expected behaviors. This is due to the way Qt handled DPI scaling prior to Qt6. Qt::HighDpiScaleFactorRoundingPolicy defaulted to So this situation is at least improved in the nightly Win64 builds because they use Qt6 now after @jurplel switched from Azure Pipelines to GitHub Actions. As for the Win32 builds, the same improvement would be possible with a small code change. |
I dont know about macOS, but I think the first way is the correct way. I think the same way as I would about a movie. and web browsers do it so that the web layout don't gets messed up. |
I implemented an option called "Zoom level is relative to screen pixels" in my repo to make 1 image pixel equal 1 screen pixel @ 100% zoom level. Maybe that or something similar could be integrated into the official qView some day. It was a little tricky to get right and handle the window getting dragged across different displays with varying scaling settings or the scaling setting getting changed on the current display, but I think I got it all working. |
I would be interested in a PR with this change + your change for the PassThrough tweak above Awesome work |
I always thought that was what "%100 size" or "natural size" was. and at least in xorg it is. |
This fix would be very much appreciated, it's the only big issue keeping me from using qView at the moment, because I need to see the pixel perfect versions of my photos and not a scaled version. Thank you all for your hard work :) |
This would be an important settings in qView, without a doubt. Please consider this. All images on Windows at Original size are blurry for anyone using higher DPI scaling. I assume that this is a non-issue for anyone with their Windows scaling set to 100%. However, at 125%, 150%, etc. you are not seeing the image as you should. When you open the same images in GIMP or other image viewers, the images are not stretched at original size. qView seems to stretch images in the same way that web browsers do and it just makes them all blurry at original size. Anyway, I see that PR from @jdpurcell that fixes this issue. Thank you. I'm going to build from that PR for now and use that until it is merged. Cheers! |
Please consider releasing this as a new version. I love qView but now that I'm using a 4k screen the images are indeed scaled up beyond their actual resolution. So even viewing the original size is blow up slightly and appears blurrier. I would love to have the option to view pixel 1:1. Sadly I have no experience how to build an installer myself from PR. |
@gopgnz This repo thankfully has automated builds, the Windows build from the latest run of my PR #699 is here. If you're curious how to find those links in the future, if you go to my PR and scroll near the bottom where it says "All checks have passed" and click "Show all checks". Then click Details for any one of them, and near the top left click Summary. At the bottom of that summary page are the download links for the automated build. |
@jdpurcell Thanks a lot! Especially for the quick reply! I just tested it and it works exactly like I hoped. Now the images are viewed at the exact scale. Thanks a lot! |
Environment:
OS:
Windows 10 64bit
20H2
19042.685
Display resolution : 3840x2160
qView version: 4.0
Information:
When system Settings "Display"-"Scale and layout" is above 100%, "Original size" gets incorrect size.
So I rolled back to version 3.0.
The text was updated successfully, but these errors were encountered: