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 107607 - Allow changing the tiling/scaling/rotating of the background image
Allow changing the tiling/scaling/rotating of the background image
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: panel
git master
Other All
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
new-toplevel-todo
Depends on:
Blocks:
 
 
Reported: 2003-03-05 04:11 UTC by Mark McLoughlin
Modified: 2020-11-06 20:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10

Attachments
Proposed patch (29.97 KB, patch)
2009-05-06 15:31 UTC, Cody Russell 		none Details | Review

Description Mark McLoughlin 2003-03-05 04:11:35 UTC 
The new properties dialog doesn't allow you to change the "fit",
"stretch" and "rotate" background image properties. Need to be
able to do that.
                                                                          
                                  
I'm thinking it might be best to move the image configuration to
a seperate dialog invoked from a "Configure Image" button or
something.
Comment 1 Cody Russell 2009-05-06 15:31:19 UTC 
Created attachment 134110 [details] [review]
Proposed patch

I'm not a fan of creating a new dialog for this, it seems that it would fit very well into the existing properties dialog.  Here is a patch that would do this.
Comment 2 André Klapper 2020-11-06 20:20:13 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.