Implement the new designed interface for fingerprint enrollment, so that the dialog is now based on a stack of views: - A list of devices to choose (shown only if multiple are available) - A gallery of enrolled prints available where manage them - An enrollment progress view when enrolling a new finger Move part of the logic into a new FingerprintManager (to manage gdbus proxies generated via gdbus-codegen) that is created when configuring the current user and that tracks the devices states, while move most of the UI into a new CcFingerprintDialog that does all the operations in async way. Due to fprintd lack of APIs, there are few features missing, compared to the final design (none is a regression): - Identify the finger when the enroll dialog is visible - Delete a single fingerprint - Highlight the finger when the sensor is touched during enrollment - Add customized labels to fingerprints - Devices hotpluging However most of the code has been written considering these, and so they could be easily implemented in future re-iterations once newer APIs are defined for such bits. Closes https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 |
||
---|---|---|
.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.
Reporting Bugs
Before reporting any bugs or opening feature requests, read the communication guidelines.
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
- Exact error message
- Steps to reproduce the bug
- If the bug is a visual defect, attach a screenshot
- If the bug is a crash, attach a backtrace if possible [see below]
How to get a backtrace
If the crash is reproducible, follow the steps to obtain a backtrace:
Install debug symbols for gnome-control-center.
Run the program in gdb [the GNU debugger] or any other debugger.
gdb gnome-control-center
Start the program.
(gdb) run
Reproduce the crash and when the program exits to (gdb) prompt, get the backtrace.
(gdb) bt full
Once you have the backtrace, copy and paste it into the 'Comments' field or attach it as a file to the bug report.
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.