A fork of Gnome-control-center with some tweaks
Find a file
Georges Basile Stavracas Neto 60b235754e keyboard: move keyboard management code to custom class
Instead of having CcKeyboardPanel managing both UI and backend code,
factor the backend code to a new CcKeyboardManager class and drop
backend management from the panel itself.

The new backend class handles the loading, creation and removal and
search of keyboard shortcuts. It also resolves reversible shortcuts
when searching.

This patch moves the code to this new class, and updates the rest of
the Keyboard panel to use it instead.

https://bugzilla.gnome.org/show_bug.cgi?id=769063
2016-07-29 13:43:47 -03:00
libgd@2899de073f
m4
man
panels keyboard: move keyboard management code to custom class 2016-07-29 13:43:47 -03:00
po keyboard: introduce CcKeyboardShortcutEditor 2016-07-29 13:43:47 -03:00
search-provider
shell shell: ensure valid data when loading the panel 2016-07-26 11:59:07 -03:00
.gitmodules
AUTHORS
autogen.sh
ChangeLog
configure.ac mouse: Offer a separate option for edge scrolling 2016-07-27 17:40:30 +02:00
COPYING
git.mk
gnome-control-center.doap
MAINTAINERS
Makefile.am
Makefile.decl build: Add GTest Makefile snippet 2016-06-10 15:04:44 +02:00
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.