A fork of Gnome-control-center with some tweaks
0f53df3f1d
2004-04-07 Jody Goldberg <jody@gnome.org> * gnome-theme-manager.c (update_settings_from_gconf_idle) : fix the selection when not running metacity. That was damn irritating. 2004-03-10 Chris Lahey <clahey@ximian.com> * gnome-theme-manager.c: (pixbuf_async_func): rename function. Use broken_image. (pixbuf_async_data_free): rename function. Use PixbufAsyncData instead of a GList. (pixbuf_idle_func): rename function. Handle the case that things change again while we're updating. Stop what it's doing and start from the beginning. (add_pixbuf_idle): (load_meta_themes): clean up. Remove model_meta_theme_info. (update_themes_from_disk): Remove the code to check for have_meta_theme here. It works with no metathemes installed. (add_custom_row_to_meta_theme): handle the initial case too. (remove_custom_row_from_meta_theme): removed. (themes_equal): helper function for a fairly complicated comparison. (update_settings_from_gconf_idle), (update_settings_from_gconf): reamed. Instead of custom_theme_found to mean that there should be a custom theme, we use current_theme_saved. This means that there's a metatheme for the current theme. Its meaning is almost exactly the boolean opposite of the old one but it's more understandable. initial_theme_saved tells us whether the initial theme has a metatheme for it now. (theme_changed_idle), (theme_changed_func): Made this idle to reduce rerunning (setup_dialog): Load broken image. (gnome_theme_manager_sort_func): Make it symmetric. * gnome-theme-manager.h: Remove THEME_FLAG_INITIAL. |
||
|---|---|---|
| archiver | ||
| capplets | ||
| control-center | ||
| debian | ||
| gnome-settings-daemon | ||
| help | ||
| idl | ||
| libbackground | ||
| libwindow-settings | ||
| po | ||
| root-manager | ||
| schemas | ||
| typing-break | ||
| vfs-methods | ||
| .cvsignore | ||
| acinclude.m4 | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.in | ||
| control-center.spec.in | ||
| control-center2.png | ||
| 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 one of the people listed in the MAINTAINERS file. 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 -u file-to-be-patched.c > patch.diff