A fork of Gnome-control-center with some tweaks
2006-01-26 Rodney Dawes <dobey@novell.com> * gnome-background-properties.glade: Add an Apply button * gnome-wp-capplet.[ch]: Replace old_filename with an old_item struct (gnome_wp_props_wp_set): Set the filename key to empty string when setting the background to "No Wallpaper" (gnome_wp_props_revert): New method to revert changes in the dialog when the Cancel button is clicked (gnome_wp_main_quit): Free the old_item structure (wallpaper_properties_clicked): Handle the Apply button Handle closing the dialog for OK separately from Cancel/delete_event Revert the settings when Cancel or wm "x" or ESC are clicked (gnome_wp_load_stuffs): Set the old_item to the currently selected background setting, whether it be an image or "No Wallpaper" * gnome-wp-info.c (gnome_wp_info_dup): If info is NULL, just return NULL rather than trying to access members of an empty struct * gnome-wp-item.[ch] (gnome_wp_item_dup): New method to create a duplicate and newly allocated GnomeWPItem structure Fixes #327335 |
||
---|---|---|
archiver | ||
capplets | ||
control-center | ||
debian | ||
gnome-settings-daemon | ||
help | ||
idl | ||
libbackground | ||
libwindow-settings | ||
m4 | ||
po | ||
root-manager | ||
schemas | ||
typing-break | ||
vfs-methods | ||
.cvsignore | ||
AUTHORS | ||
autogen.sh | ||
ChangeLog | ||
configure.in | ||
control-center.spec.in | ||
COPYING | ||
MAINTAINERS | ||
Makefile.am | ||
NEWS | ||
README | ||
TODO | ||
TODO.xml |
GNOME Control Center ==================== Requirements - intltool >= 0.21 gtk+ >= 2.3.0 gconf >= 2.0.0 libgnome >= 2.0.0 libgnomeui >= 2.0.0 libglade >= 2.0.0 libbonobo >= 2.0.0 libbonoboui >= 2.0.0 libgnomevfs >= 2.0.0 gnome-desktop >= 2.0.0 gnome-icon-theme >= 1.1.3 Installation - See the file 'INSTALL' How to report bugs - Bugs should be reported to the GNOME bug tracking system under the product control-center. It is available at http://bugzilla.gnome.org. In the report please include the following information - Operating system and version For Linux, version of the C library How to reproduce the bug if possible If the bug was a crash, include the exact text that was printed out A stacktrace where possible [see below] How to get a stack trace - If the crash is reproducible, it is possible to get a stack trace and attach it to the bug report. The following steps are used to obtain a stack trace - Run the program in gdb [the GNU debugger] or any other debugger ie. gdb gnome-calculator Start the program ie. (gdb) run Reproduce the crash and the program will exit to the gdb prompt Get the back trace ie. (gdb) bt Once you have the backtrace, copy and paste this either into the 'Comments' field or attach a file with it included. Patches - Patches should be submitted to bugzilla.gnome.org or emailed to the gnomecc-list@gnome.org list. If using bugzilla, attach the patch to a new bug report [or preferably, check to see if there is already a bug report that corresponds to your patch]. Bug reports containing patches should include the 'PATCH' keyword. Patches should be created using the unified diff form. ie. cvs diff -up file-to-be-patched.c > patch.diff