After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 748712 - Bad zoom out algorithm, causing artifacts
Bad zoom out algorithm, causing artifacts
Status: RESOLVED DUPLICATE of bug 665897
Product: eog
Classification: Core
Component: image viewer
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-04-30 15:46 UTC by Boris Gjenero
Modified: 2016-03-30 13:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Example of lines which cause artifacts (38.03 KB, image/jpeg)
2015-04-30 15:46 UTC, Boris Gjenero
Details

Description Boris Gjenero 2015-04-30 15:46:10 UTC
Created attachment 302671 [details]
Example of lines which cause artifacts

When an image is viewed scaled down, it looks wrong. Diagonal lines which are smooth at 100% get a pixelated staircase appearance. Parts of lines can disappear, making a solid line into a dashed line, and moire patterns can arise. Small bright or dark areas can end up as a single bright or dark pixel which inappropriately stands out.

This can be seen in the screenshot of what are apparently plant seeds at: https://wiki.gnome.org/Apps/EyeOfGnome , in particular https://wiki.gnome.org/Apps/EyeOfGnome?action=AttachFile&do=get&target=screenshot.png . You can see how filaments which  are in focus get a staircase or even dashed (discontinuous) appearance. I am also attaching a small sample which causes this effect.

The "Smooth images when zoomed out" option makes a small difference, but doesn't come close to fixing this problem.
Comment 1 Felix Riemann 2016-03-30 13:31:30 UTC
Filtering should be better in eog-3.20 now.
---
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 665897 ***