GNOME Shell

gnome-shell:wip/fmuellner/overview-keynav

  1. Git
  2. lp:gnome-shell
  3. wip/fmuellner/overview-keynav
Last commit made on 2018-08-01
Get this branch:
git clone -b wip/fmuellner/overview-keynav https://git.launchpad.net/gnome-shell

Branch merges

Branch information

Name:
wip/fmuellner/overview-keynav
Repository:
lp:gnome-shell

Recent commits

38c05d9... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

workspacesView: Enable keynav between all monitors

Instead of using one focus group for each (per-monitor) workspacesView,
use a single one that is shared between all of them.

https://gitlab.gnome.org/GNOME/gnome-shell/issues/412

eeda54f... by Bruno Lopes da Silva

Update Brazilian Portuguese translation

b8b5da1... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

Bump version to 3.29.90

Update NEWS.

3a9ad5c... by Piotr Drąg

Update POTFILES.in

d57dc94... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

tools: Migrate changed overrides settings

While the new per-desktop overrides in GIO are easier to use for
both developers and users, it is still inconvenient for everyone
who changed the defaults using the old overrides hack to lose
their settings. Address this by running a small script on startup
that migrates existing settings.

https://bugzilla.gnome.org/show_bug.cgi?id=786496

393d724... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

Replace custom override schema with per-desktop override

GSettings now recognizes per-desktop overrides that can be used
to change schemas' default values for a particular desktop. This
is not entirely unlike our existing custom override mechanism in
mutter, except that it is not limited to keys in org.gnome.mutter,
and it doesn't require a separate schema - the latter means that
we (and gnome-teak-tool) no longer have to figure out the correct
schema for the current login session and just use the original one.

https://bugzilla.gnome.org/show_bug.cgi?id=786496

6217c3b... by Didier Roche-Tolomelli

volume: Show overamplified icon when in overdrive

Show an overamplified volume icon if volume is louder the max normalized one.
Use a similar logic as gnome-settings-daemon to delimit values, restricted
to output.
The purpose is to help users remember that visiting some websites or
using some apps can get LOUD.

https://bugzilla.gnome.org/show_bug.cgi?id=790280.

ddd4fd9... by Didier Roche-Tolomelli

barLevel: Add "overdrive" capability

Implement for barLevel an overdrive area. This is a zone represented via a
different styling to indicate that you are bypassing the normal zone of
a given level, without reaching yet the maximum limit.

https://bugzilla.gnome.org/show_bug.cgi?id=790280.

d2a97e7... by Didier Roche-Tolomelli

volume: Allow volume above 100%

Depending on hardware and recorded volume level, turning up the speakers
to the maximum volume may not be enough and the user will want to amplify
the volume above 100%. Currently this requires opening the sound Settings
panel which gets cumbersome when required repeatedly.

To support this case better, allow raising the sound volume above 100%
directly from the system menu if the feature is enabled via the
`allow-volume-above-100-percent` key in `org.gnome.desktop.sound`.

aa75e89... by Didier Roche-Tolomelli

osdWindow: Allow levels above 100%

Allow osd representing levels that can be more than 100% by accepting
an optional parameter setting that maximum level.
gnome-settings-daemon will use this to indicate volume levels above 100%,
which our own volume indicator will soon support as well.