GitLab

There are usually 2 reasons why the agent might go away:
- we're switching panels in the Settings
- the Settings executable is exit()ing

In the former case, we can't actually do anything if unregistering the
agent fails, and we can already remove our object path without waiting
on anyone, so just print some debug if it fails.

In the latter case, we'll be gone from the bus before before the method
has time to answer.

This fixes possible hangs while unregistering the agent when switching
panels with some broken Bluetooth adapters and/or drivers.

Closes: #49

Sort devices by the time a row was created for them. This means that
newly discovered devices should appear at the bottom of the list, rather
than the top, making it less likely that the widget under the mouse or
finger would change before it's clicked.

This should also make the list of setup devices more static even if
the device names are changed.

Closes: #55

This captures when the device was discovered, or when a widget was
created for it, which should be good enough to know when a particular
device was discovered after another.

In case we exit quickly.

Connect to the dialogue's "response" signal so that the dialogue is
closed when "Cancel" gets clicked.

Closes: #52

Instead of eating it.

In some circumstances, setting the discovery mode might be a bit long,
usually because there's another action pending, so send it async. D-Bus
guarantees that the messages will get to the daemon in the same sequence
we sent them, so we're just delaying the changes a bit.

Clear warnings are better than crashes.

Now that we require a new enough version of BlueZ.

The fix in commit 274b856f was overly
aggressive and did not create any rows for devices that appeared and
didn't have a name. The problem is that the rows were also not created
when that name appeared.

Always create rows for devices which we might end up showing but mark
them as invisible until a name is present.

Implement setting the 'Powered' property ourselves to make sure that it
doesn't throw a warning when the adapter is blocked through rfkill.

Closes: #6

The joypad quirk has been merged in BlueZ's autopair plugin in version
5.51, released in 2019.

#36
https://bugzilla.gnome.org/show_bug.cgi?id=790906

This stops invalid agent object paths from being registered, and failing
deeper inside the library.

It was declared, and exported, but never defined.

It was used by the autotools. We have a map file instead now.

Using g_auto*