08a7f7cb53
This adds the following API: * cc_display_config_get_ui_sorted_monitors Returns the monitors in UI order * cc_display_config_count_useful_monitors Counts the useful monitors (active and usable) * cc_display_monitor_is_useful Checks if a monitor is active and usable * cc_display_monitor_is_useable Check if a monitor is marked as useable * cc_display_monitor_set_usable Used to mark builtin monitors as unusable if the lid is closed * cc_display_monitor_get_ui_* Get the UI number and strings for display https://bugzilla.gnome.org/show_bug.cgi?id=786971 |
||
|---|---|---|
| .gitlab/issue_templates | ||
| build-aux | ||
| data/icons | ||
| docs | ||
| gettext/its | ||
| man | ||
| panels | ||
| po | ||
| search-provider | ||
| shell | ||
| subprojects | ||
| tests | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| COPYING | ||
| gnome-control-center.doap | ||
| meson.build | ||
| meson_options.txt | ||
| NEWS | ||
| README.md | ||
GNOME Settings
GNOME Settings is GNOME's main interface for configuration of various aspects of your desktop.
Contributing
See docs/CONTRIBUTING.md for details on the contribution process, and docs/HACKING.md
for the coding style guidelines.
Testing Unstable Settings
It is quite easy to test and give feedback about the development version of GNOME Settings. Just access https://gitlab.gnome.org/GNOME/gnome-control-center/environments, get the latest version, download it, double-click the file, install and run.
Note that GNOME Settings Flatpak will only work if you are running the latest GNOME version in your host system.
Reporting Bugs
Bugs should be reported to the GNOME bug tracking system under the product gnome-control-center. It is available at GitLab Issues.
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.