Add a drop-shadow to the device icon to work-around the fact that the
mouse icon would be gray on gray in the default style.

Closes: gnome-control-center#2284

As mentioned in the previous commit, the invisible character will only
be set to non-zero if the entry is set to show invisible characters.

Make sure to set the entry to hide characters so the invisible character
is set to a usable value.

The invisible character we fetch from an entry might be zero if it
isn't set, for example when the entry isn't setup to hide text. This
would result in the passkey that's displayed being truncated as the
invisible character would be a nul terminator.

Make sure we have a valid invisible character, so the passkey doesn't
disappear after the first typed character when pairing a keyboard with
typing notification.

Closes: #125

Jake Dane authored Sep 11, 2022 and Bastien Nocera committed Sep 12, 2022

The X-GNOME-Bugzilla-* entries were for use by bug-buddy, a GNOME 2
technology that's been gone for over a decade. These entries are
obsolete and can be removed.

The serial for Bluetooth devices is the Bluetooth address, make sure to
export it.

Handle the battery information for a device even if it is available
from a source other than bluetoothd in the upower output.

This means getting battery information from the more authoritative
kernel-supported protocol on Logitech devices, as well as being able to
have battery information for Bluetooth classic devices like Apple
input devices.

See https://gitlab.freedesktop.org/upower/upower/-/merge_requests/166

The bluetooth-sendto man page still mentioned that a device chooser
would be shown if a device address wasn't passed, but that's not the
case since GNOME 42, where all the device chooser widgets were removed.

Use new adapter property in bluez to implement the
default-adapter-state. It should work better, as it doesn't rely only on
internal BluetoothClient state in a single process, and can get
information when bluetoothd is powering up the adapter.

Note that this property still works in the absence of a new enough
bluetoothd, without the transitional states.

Closes: #121

Add enum type generation code to the gir sources. This fixes enum types
showing up as 'undefined' in gjs.

The change did not impact Python.

--✀--
const {Gio, GLib, GnomeBluetooth, GObject} = imports.gi;

client = new GnomeBluetooth.Client();
client.connect('notify', () => {
        print(client.default_adapter_state);
});

ml = new GLib.MainLoop(null, false);
ml.run()
--✀--

Unfortunately, powering on/off Bluetooth adapters has become longer,
and less reliable over time, so front-ends need more information to
be able to figure out what it happening.

As a first pass, export whether the adapter is in the process of being
turned on, or turned off, based on our own request.

Traceback (most recent call last):
  File "/builds/GNOME/gnome-bluetooth/_build/../tests/integration-test.py", line 429, in test_connectable_devices
    self.assertEqual(list_store.get_n_items(), 3)
AssertionError: 0 != 3

Better explain what _connect_service() does, so it's not used for
devices which can't be "connected" to.

Maximiliano authored Jul 15, 2022 and Bastien Nocera committed Jul 15, 2022

Makes the window look better.

Adds support for dark mode.

Fixes: #114

Can't really explain the purpose of this variable by just naming it, so
document it in the structure that defines it.

Reorganise functions called from
_bluetooth_client_set_default_adapter_discovering() so that we only call
StartDiscovery() if SetDiscoveryFilter() is successful, and we disable
the "in-flight" ->discovery_started variable so the next default-adapter
changes would try to enable discovery again if needed.

Closes: #100

When somebody requests the "default-adapter-setup-mode" to be disabled
but there's no default adapter, consider that we're not in setup mode.