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 554446 - eog window window border should minimize around the picture at best fit
eog window window border should minimize around the picture at best fit
Status: RESOLVED DUPLICATE of bug 530447
Product: eog
Classification: Core
Component: image viewer
2.22.x
Other All
: Normal minor
: ---
Assigned To: EOG Maintainers
EOG Maintainers
: 551917 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-09-30 14:51 UTC by mr. adams
Modified: 2008-10-08 19:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description mr. adams 2008-09-30 14:51:32 UTC
Is there a way to reset the default window size in relation to image
size in EyeOfGnome?

I find that opening an image of almost any size (or viewing it at Best
Fit) there is invariably an empty space of approximately 125px to the
left and right of the image. Is it possible to "minimize" the border
area around the image (upon launching eog)? I often find myself manually
resizing the window pane along the horizontal access.

I simply don't understand what the empty screen real-estate to the left
and right of the image within the EOG window is for. This is a feature request or a usability complaint, depending upon how you look at it.

Other information:
I was requested to cross-post this feature request from launchpad to here:

https://bugs.launchpad.net/bugs/269287
Comment 1 Felix Riemann 2008-10-08 16:40:55 UTC
*** Bug 551917 has been marked as a duplicate of this bug. ***
Comment 2 Felix Riemann 2008-10-08 16:49:39 UTC
I guess you're seeing this with the collection hidden.
Then this is related to bug 530447.
Comment 3 Felix Riemann 2008-10-08 19:10:13 UTC
(In reply to comment #2)
> Then this is related to bug 530447.
> 
Yup, just checked myself. This was also caused by above bug. According to the schedule the fix will ship with 2.24.1.
----------------------------------------------------------------------
Thanks for taking the time to report this bug.
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. It should be solved in the next software version. You may want to check for a software upgrade.


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