A fork of Gnome-control-center with some tweaks
After introducing the reset button to match the mockups [1], the shortcut editor dialog had some issues exposed. This is visible e.g. when the user tries to edit a custom shortcut's name and the shortcut is disabled. This happens because we assume there is always a shortcut set. When we open the dialog to edit a custom shortcut, however, nothing is actually set, and we end up saving the disabled shortcut when editing the shortcut's name or command. Fix that by initializing the shortcut's accelerators when editing a shortcut, and correcting the logic to validate the shortcut. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/keyboard/keyboard-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=777845 |
||
---|---|---|
libgd@752f65e91e | ||
m4 | ||
man | ||
panels | ||
po | ||
search-provider | ||
shell | ||
.gitmodules | ||
AUTHORS | ||
autogen.sh | ||
ChangeLog | ||
configure.ac | ||
COPYING | ||
git.mk | ||
gnome-control-center.doap | ||
MAINTAINERS | ||
Makefile.am | ||
Makefile.decl | ||
NEWS | ||
README | ||
update-from-gsd.sh |
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 gnome-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. See https://live.gnome.org/GnomeLove/SubmittingPatches for how to create patches.