A fork of Gnome-control-center with some tweaks
Find a file
Georges Basile Stavracas Neto 4ad1c5dea1 wifi: Expose Airplane Mode row outside access point list
The current Wi-Fi panel ties the Airplane Mode row to the access
point list of a given Wi-Fi adapter. That has unintended but
bad side effects: when enabling Airplane Mode, the row disappears
and we have to switch to another panel (e.g. Bluetooth) in order
to disable it. This is functionally wrong: we should be able to
enable or disable Airplane Mode from where we initially changed
it.

This commit reorganizes the widget hierarchy in order to put the
Airplane Mode row outside of the main GtkStack page. This is
necessary in order to fully implement the proposed mockups[1]
and, in general, because it's the right thing to do.

Notice that the logic of the empty states in [1] is not fully
implemented yet; this commit only reorganizes the widgets that
already exist to get closer to the mockups. Subsequent commits
will implement more of the empty states.

[1] https://github.com/gnome-design-team/gnome-mockups/raw/master/system-settings/network/aday3/wi-fi-wires.png

Fixes https://gitlab.gnome.org/GNOME/gnome-control-center/issues/121
2018-07-23 12:55:59 +00:00
.gitlab/issue_templates project: Add issue templates 2018-05-02 21:02:13 -03:00
build-aux CI: build flatpak using the "official" Docker image 2018-07-17 15:06:34 -03:00
data/icons project: Update meson files 2018-05-03 00:45:29 -03:00
docs project: Document maintainers and workflow 2018-07-16 20:50:12 -03:00
gettext/its build: Fix translation context missing from keyboard entries 2018-01-24 20:43:34 +01:00
man project: Update meson files 2018-05-03 00:45:29 -03:00
panels wifi: Expose Airplane Mode row outside access point list 2018-07-23 12:55:59 +00:00
po network: Rename UI files to match C files 2018-07-23 12:55:59 +00:00
search-provider project: Update meson files 2018-05-03 00:45:29 -03:00
shell shell: Rename .ui files to match .c files 2018-07-18 21:34:09 +00:00
subprojects build: Drop libgd 2018-03-16 15:55:10 -03:00
tests tests: increase the tests timeout 2018-07-15 01:47:24 +00:00
.gitignore project: Update gitignore 2018-05-12 20:56:04 -03:00
.gitlab-ci.yml CI: build flatpak using the "official" Docker image 2018-07-17 15:06:34 -03:00
.gitmodules git: Remove libgd from .gitmodules 2018-03-23 10:46:52 -03:00
COPYING build: Update COPYING with new mailing address 2012-08-22 15:33:18 +01:00
gnome-control-center.doap project: Document maintainers and workflow 2018-07-16 20:50:12 -03:00
meson.build 3.29.4 2018-07-16 21:32:05 -03:00
meson_options.txt window: Warn about development builds 2018-05-14 18:24:03 -03:00
NEWS 3.29.4 2018-07-16 21:32:05 -03:00
README.md docs: add the coverage badge 2018-07-05 23:25:23 +00:00

Build Status Coverage report License

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.