A fork of Gnome-control-center with some tweaks
4d87d80f3e
2004-06-28 Rodney Dawes <dobey@novell.com> * *.[ch]: Update copyright info to have correct years (2003-2004) * gnome-wp-capplet.c (gnome_wp_capplet_scroll_to_item): Abstract this code out so that we don't have to duplicated it every time we want to scroll to a particular item in the list (gnome_wp_add_image): Update this to return the new item that we created, and don't scroll to or set as the wallpaper, every time we call this function Use the new gnome_wp_item_new () call to create items (gnome_wp_add_images): Change the API to not use the files argument any longer, as we don't need it without the GTK+ 2.2 compat code Add all the items to the list and select the last one when finished (gnome_wp_file_open_dialog): Update to not pass in the files argument to gnome_wp_add_images () and free the GSList of filenames (bg_add_multiple_files): merge this code into the normal callback for when images are dragged to the dialog (bg_properties_dragged_image): Don't check if the list is more than 1 or not here, and always call gnome_wp_add_images () with the full list that we are given Convert the GList of GnomeVFSURIs that we get from gnome-vfs to a GSList of char * uris to pass into gnome_wp_add_images () (gnome_wp_load_stuffs, gnome_wp_file_changed): Use the new gnome_wp_capplet_scroll_to_item () and gnome_wp_item_new () API calls instead of duplicating code * gnome-wp-capplet.h: Remove the GConf key path defines from here * gnome-wp-item.[ch]: Add the gnome_wp_item_new () call to create the GnomeWPItem structure for storing wallpapers in * gnome-wp-utils.h: Put the GConf key path defines in here * gnome-wp-xml.c (gnome_wp_load_legacy): Use the gnome_wp_item_new () call to create items from the old legacy (XD2 capplet) list file |
||
|---|---|---|
| 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