A fork of Gnome-control-center with some tweaks
324f02cea3
+ + * Merge randr-12 to trunk + +Tue Jun 17 18:29:46 2008 S�ren Sandmann <sandmann@redhat.com> + + * Port to changes in gnome-desktop + +2008-06-04 Federico Mena Quintero <federico@novell.com> + + * xrandr-capplet.c (driver_is_randr_10): New function, currently + unused, to detect whether the graphics driver used in the X server + only supports the RANDR 1.0 API. We may find this information + useful to tell the user that not all the features in the capplet + will work as intended, or to actually disable features that won't work. + +2008-05-29 Federico Mena Quintero <federico@novell.com> + + * xrandr-capplet.c (apply): Before applying the settings, check if + the X server supports the Virtual size we need. + (check_required_virtual_size): New function; does the checking + against what the X server supports. + This still needs to present a friendly dialog box. + (compute_virtual_size_for_configuration): New function. + +Wed May 14 18:16:10 2008 S�ren Sandmann <sandmann@redhat.com> + + * xrandr-capplet.c: Add GNOME_DESKTOP_USE_UNSTABLE_API define + + * scrollarea.[ch]: Add copyright statement + +2008-05-14 Soren Sandmann Pedersen <sandmann@redhat.com> + + * *: Check in new RandR 1.2 enabled capplet + svn path=/trunk/; revision=8762 |
||
|---|---|---|
| capplets | ||
| help | ||
| libwindow-settings | ||
| po | ||
| shell | ||
| typing-break | ||
| vfs-methods | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.in | ||
| COPYING | ||
| MAINTAINERS | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| TODO | ||
GNOME Control Center ==================== About - The control center is GNOME's main interface for configuration of various aspects of your desktop. 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-keyboard-properties 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 full 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. svn diff file-to-be-patched.c > patch.diff