Set Desktop Background could choose style (Zoom or Scale) heuristically
Submitted by Adam Dingle
Link to original bug (#716390)
Description
---- Reported by adam@yorba.org 2010-06-21 14:33:00 -0700 ----
Original Redmine bug id: 2177
Original URL: http://redmine.yorba.org/issues/2177
Searchable id: yorba-bug-2177
Original author: Adam Dingle
Original description:
From Martin Olsson mnemo@minimum.se:
What I propose is that Shotwell chooses the “style†setting
based on some smarter heuristics.
Maybe you will see what I mean if I provide another example. Download
this image and set it as desktop background using zoom:
http://upload.wikimedia.org/wikipedia/commons/e/e9/A.J._Bowen._Sundance_2007.j pg
Since the image is so tall, it just doesn't look good. Especially on wide
screens. For example, this is what I see:
http://temp.minimum.se/shotwell_other/cropped_portrait.png
Using SCALE in this case with explictly set BLACK background color looks better:
http://temp.minimum.se/shotwell_other/scale_looks_better.png
Granted, some users will want to use “zoom†anyway for certain photos,
for example here is another portrait which actually zoom really good in
http://temp.minimum.se/shotwell_other/accidentally_looks_really_good.png
http://upload.wikimedia.org/wikipedia/commons/d/d1/Portrait_Gandhi.jpg
So to conclude; the argument I'm trying to make here is that I believe that
for tall photos, using SCALE + explicit black will be what users what more
often than using ZOOM.
Of course for all photos with landscape orientation (that is width > height),
zoom is clearly the right choice.
--- Bug imported by chaz@yorba.org 2013-11-25 21:45 UTC ---
This bug was previously known as bug 2177 at http://redmine.yorba.org/show_bug.cgi?id=2177
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution