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 355107 - Do not add borders before saving thumbnails
Do not add borders before saving thumbnails
Status: RESOLVED INVALID
Product: nautilus
Classification: Core
Component: Thumbnails
2.14.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 425745 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-09 12:28 UTC by Mukund Sivaraman
Modified: 2007-04-13 10:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Mukund Sivaraman 2006-09-09 12:28:09 UTC 
Please describe the problem:
Some Nautilus thumbnails have a border around them while others don't. It seems like apps which create their own thumbnails for their image data (GIMP for XCF for example) save the raw thumbnail, where as Nautilus adds the border for thumbnails it creates. The end result is an inconsistent look on the Desktop and folder windows. A better approach would be to store thumbnails as-is and add the border before drawing it to the screen (would take slightly longer to display).



Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Mukund Sivaraman 2006-09-09 12:32:06 UTC 
Hey, on further checking I think I'm wrong on this one. The thumbnails do not have borders. But I still have an inconsistent Desktop display with some thumbnails having a border and others not. What's causing it?
Comment 2 Jaap A. Haitsma 2006-09-09 15:26:43 UTC 
There is logic in the function load_icon_file of nautilus-icon-factory.c

Basically it depends on the size of the image and if the image has a transparency layer (in that case it's probably an icon and a frame would look bad)
Comment 3 Michael Chudobiak 2007-04-13 10:05:54 UTC 
*** Bug 425745 has been marked as a duplicate of this bug. ***