A fork of Gnome-control-center with some tweaks
4622d5ed51
2006-02-09 Rodney Dawes <dobey@novell.com> * gnome-background-properties.glade: Replace the Apply/Cancel/OK buttons with a Finish button, using the stock apply icon * gnome-wp-capplet.c (gnome_wp_props_wp_set): Don't need to check if we are the same image as we were before now (gnome_wp_props_revert): Remove this as it is no longer needed (gnome_wp_props_wp_selected): Call the set function here (gnome_wp_main_quit): Remove the freeing of capplet->old_item (wallpaper_properties_clicked): Only handle GTK_RESPONSE_OK as an action to close the dialog now, as we are instant apply again (gnome_wp_scale_type_changed, gnome_wp_shade_type_changed): (gnome_wp_color_changed): Set the appropriate gconf keys here (gnome_wp_load_stuffs): Remove references to capplet->old_item * gnome-wp-capplet.h (struct _GnomeWPCapplet): Remove old_item object Fixes #327335, #330587 and #329818 Partially fixes #330168 |
||
|---|---|---|
| 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