Ian Douglas Scott

https://github.com/pop-os/cosmic-applets/pull/492 should fix this.

https://github.com/pop-os/cosmic-osd/pull/19 has an Iced subscription to monitor to speaker/microphone volume levels. It might be helpful to move some of the code there into a library that could also be used...

Per-device input settings are supported in cosmic-comp now with an `input_devices` setting, but aren't exposed in the UI. But this doesn't include keyboard layout. Keyboard layout works a bit differently...

In mutter a `MetaWorkspace` is [associated with](https://developer.gnome.org/meta/stable/MetaWorkspace.html#meta-workspace-get-screen) a particular `MetaScreen`, but as given the existence of a `meta_screen_get_n_monitors` function, this probably isn't quite what it sounds like. Presumably this is...

Mutter does support "Workspaces only on primary monitor" (which is the default behavior), which can be enabled through gsettings or Gnome Tweaks. Though this isn't what we want. It seems...

> (and perhaps other brands if possible) It seems keyboard *brightness* is already controllable over dbus with the `org.gnome.SettingsDaemon.Power.Keyboard` schema [defined by gnome-settings-daemon](https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/blob/master/plugins/power/gsd-power-manager.c), which seems to be just a wrapper...

Actually (and I guess unsurprisingly) it looks like Gnome Control Center can already control keyboard brightness under `Power→Power Saving`. However we design this, we probably want to avoid duplication, while...

> In terms of the color chooser we can use that if that would make implementation easier `GtkColorChooserDialog` is built into Gtk, so it's certainly simpler to use that, rather...

> Logically, the left to right axis on that screenshot would map to brightness[...] Or rather, to use the proper color theory terminology: `GtkColorChooser` allows the user to select any...