File talk:Mixed-mode scaling.png
![]() | This orphaned CSD G8 as it has been asserted to be useful to Wikipedia.If you believe it should be deleted, please nominate it on Wikipedia:Miscellany for deletion. |
For all those who dispute the fair-use status
(Pinging @JJMC89: as he/she started questioning this image's purpose)
- Criterion 3a: The three non-free images illustrate significantly different things. Unlike the latter two (which simply show the effect of Windows scaling at 200%), the former clearly shows the issues caused when a prominent Windows application like Visual Studio (which is per-monitor V1 aware) is moved between screens with different DPI scaling (in the disputed screenshot, from 125% to 100%). The loss of clarity is subtle, but distinct (hence why it's not low-res so that the effect is clear to the reader)
- Criterion 8: Incorrect criterion being called up, see above for the purpose of the image. The reader understands the issues with working with screens with differing DPI through this example.
- Criterion 1: Addressed on the talk page itself.
If you think that I'm not correct on my reasoning, ping me. It's awful seeing my image deleted on my back without having sufficient notice of the same (hence why I reset the expiration date).
Leaderboard (talk) 00:18, 8 December 2018 (UTC)
- @Leaderboard: 1) It is replaceable with free media by creating a screenshot using a freely licensed GUI. 3) a) One image is more then sufficient to illustrate Windows DPI scaling. b) The entire width isn't needed to illustrate the point, so it needs to be cropped at a minimum. 8) The image is not the subject of sourced critical commentary. — JJMC89 (T·C) 22:05, 8 December 2018 (UTC)
- @JJMC89: Your reasoning for (3a) is incorrect. As said above, the other images do not illustrate an issue when a window is moved between screens.
While (1) is in theory possible if you really want to go the extra mile, it could be difficult finding a free image that does have this issue (most of them do NOT implement any scaling at all). The above image still has value (potentially for the Visual Studio article?) by itself. As it stands, that is an invalid reason unless and until you can find a free substitute.
(b): Cropping is ridiculous. In fact, it needs to be expanded (unfortunately my display is only at 125% scaling, hence the subtilty).
Only (8) is sort of correct; I think I should write more about the per-monitor scaling issue. Leaderboard (talk) 23:20, 8 December 2018 (UTC)- Complying with all of the criteria is required, not going the extra mile. — JJMC89 (T·C) 04:50, 10 December 2018 (UTC)
- @JJMC89: You're clearly going too far. I can't see how a Microsoft product on a Microsoft OS not capture the problem with DPI scaling. Leaderboard (talk) 20:47, 14 December 2018 (UTC)
- Complying with all of the criteria is required, not going the extra mile. — JJMC89 (T·C) 04:50, 10 December 2018 (UTC)
- @JJMC89: Your reasoning for (3a) is incorrect. As said above, the other images do not illustrate an issue when a window is moved between screens.