gnome-shell/js/ui/status
Florian Müllner 463757569a status/bluetooth: Use promise to initialize proxy
There's no good reason for waiting for the proxy to be initialized
to connect signals. In fact, connecting the signal beforehand
ensures that the handler is in place when the proxy fetches the
properties, so we don't have to call the handler explicitly.

That in turn allows us to rely on the signal parameters to only process
changed properties.

To achieve that, construct the proxy manually, and then initialize
it asynchronously in a Promise.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2391>
2022-08-01 12:33:35 +00:00
..
accessibility.js js: Use templates for non-translatable strings 2022-02-12 12:29:52 +00:00
bluetooth.js status/bluetooth: Use promise to initialize proxy 2022-08-01 12:33:35 +00:00
brightness.js cleanup: Use new indentation style for object literals 2022-02-23 12:23:52 +00:00
dwellClick.js cleanup: Use new indentation style for object literals 2022-02-23 12:23:52 +00:00
keyboard.js Adopt EventEmitter class instead of injecting Signal methods 2022-07-04 18:30:49 -04:00
location.js js: Use (dis)connectObject() 2022-03-04 14:14:37 +00:00
network.js rfkill: Turn manager into a GObject 2022-07-19 13:27:39 +00:00
nightLight.js status/nightLight: Use promise to initialize proxy 2022-08-01 12:33:35 +00:00
power.js js: Use templates for non-translatable strings 2022-02-12 12:29:52 +00:00
powerProfiles.js status/powerProfiles: Use CHECK ornament 2022-07-27 13:39:02 +00:00
remoteAccess.js remoteAccess: Hide indicator after a timeout 2022-03-04 22:05:46 +00:00
rfkill.js rfkill: Consider HasAirplaneMode 2022-07-19 13:27:39 +00:00
system.js ui: Rename gnome-control-center to org.gnome.Settings 2022-01-21 10:44:37 -03:00
thunderbolt.js Adopt EventEmitter class instead of injecting Signal methods 2022-07-04 18:30:49 -04:00
volume.js status/volume: Add device submenus 2022-07-19 14:56:46 +02:00