Home
last modified time | relevance | path

Searched refs:ConnectToNameOwnerChangedSignal (Results 1 – 3 of 3) sorted by relevance

/external/libchrome/libchrome_tools/patches/
DConnect-to-NameOwnerChanged-signal-when-setting-call.patch6 In ObjectManager, when ConnectToNameOwnerChangedSignal is called the first time,
17 ConnectToNameOwnerChangedSignal the first time. At this point,
31 ConnectToNameOwnerChangedSignal when called. Since ObjectManager calls
131 @@ -458,6 +462,15 @@ bool ObjectProxy::ConnectToNameOwnerChangedSignal() {
138 + bool success = ConnectToNameOwnerChangedSignal();
153 bool ConnectToNameOwnerChangedSignal();
/external/libchrome/dbus/
Dobject_proxy.cc423 bool ObjectProxy::ConnectToNameOwnerChangedSignal() { in ConnectToNameOwnerChangedSignal() function in dbus::ObjectProxy
458 if (!ConnectToNameOwnerChangedSignal()) in ConnectToSignalInternal()
477 if (!ConnectToNameOwnerChangedSignal()) { // Failed to connect to the signal. in WaitForServiceToBeAvailableInternal()
Dobject_proxy.h268 bool ConnectToNameOwnerChangedSignal();