When comparing configurations, the monitor positions are compared
directly. This comparison will not work properly if one of the
configurations has an offset.
This results in the "Apply" button to show up incorrectly after moving
the top/left monitor position.
The Touchpad section looks like a single listbox
so let's handle it that way too.
This eliminates an unnecessary split in the touchpad
section that is noticeable when navigating with a keyboard.
Ensure all panels take at least 300pt of width to ensure a minimum of
usability, readability of the panels and consistency of when the shell
folds itself.
This allows to activate the already selected panel with a single click
rather than a double click, which will be needed to simply focus the
panel when the window will use a leaflet.
This is necessary for the application panel to warn that an element of
its sidebar has been activated so the window can focus on it when the
window will use a leaflet.
We were converting the floating point numbers to integers using a cast,
which causes them to be always rounded down. The result is that a
monitor may be too small by a pixel, creating broken configurations.
Also fix the same issue when calculating whether a scale should be
supported.
See https://gitlab.gnome.org/GNOME/mutter/issues/412
Our public name is Settings not Control Center.
In the description, simplify and use "system" instead of "desktop".
"GNOME desktop" is still mentioned in the summary but that seems
ok to me.
gnome-control-center's shell uses the -symbolic version
automatically. Use the icon name without the -symbolic
suffix to match what we do with other panels.
Since the gsettings is for the repeat-interval but the
GUI is for Speed, we need to reverse the mapped direction.
We have to turn off the fill indicator (has_origin) for Speed
since it fills the right side instead of the left. We turn
off the indicator for Delay to match.
Closes: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/311
The appropriate relation is already set with the mnemonic_widget property.
In particular, this also fixes an issue where a screenreader would
emit "Crosshairs" every time a new tab was entered in the Zoom dialog
because of some incorrect labelled-by relations.
