Home · Modules · All Classes · All Namespaces |
#include <TelepathyQt/_gen/svc-connection.h>
Public Slots | |
Tp::ContactAttributesMap | GetContactAttributes (const Tp::UIntList &handles, const QStringList &interfaces, bool hold, const QDBusMessage &dbusMessage) |
uint | GetContactByID (const QString &identifier, const QStringList &interfaces, const QDBusMessage &dbusMessage, QVariantMap &attributes) |
Public Member Functions | |
QStringList | ContactAttributeInterfaces () const |
![]() | |
AbstractAdaptor (const QDBusConnection &connection, QObject *adaptee, QObject *parent) | |
~AbstractAdaptor () | |
QDBusConnection | dbusConnection () const |
QObject * | adaptee () const |
Adaptor class providing a 1:1 mapping of the D-Bus interface "org.freedesktop.Telepathy.Connection.Interface.Contacts".
QStringList Tp::Service::ConnectionInterfaceContactsAdaptor::ContactAttributeInterfaces | ( | ) | const |
Return the value of the exported D-Bus object property ContactAttributeInterfaces
of type QStringList
.
Adaptees should export this property as a Qt property named 'contactAttributeInterfaces' with type QStringList.
A list of D-Bus interfaces for which GetContactAttributes is expected to work. This cannot change during the lifetime of the Connection.
ContactAttributeInterfaces
.
|
slot |
Begins a call to the exported D-Bus method GetContactAttributes
on this object.
Adaptees should export this method as a Qt slot with the following signature: void getContactAttributes(const Tp::UIntList& handles, const QStringList& interfaces, bool hold, const Tp::Service::ConnectionInterfaceContactsAdaptor::GetContactAttributesContextPtr &context);
Implementations should call MethodInvocationContext::setFinished (or setFinishedWithError accordingly) on the received context object once the method has finished processing.
Return any number of contact attributes for the given handles.
handles | An array of handles representing contacts. |
interfaces | \htmlonly <p>A list of strings indicating which D-Bus interfaces the calling process is interested in. All supported attributes from these interfaces, whose values can be obtained without additional network activity, will be in the reply.</p> <p>Connection managers SHOULD ignore interfaces requested which they do not support (i.e. those not mentioned in the \\\\endhtmlonly \\\\link requestPropertyContactAttributeInterfaces() ContactAttributeInterfaces \\\\endlink \\\\htmlonly property.)</p> <div class="rationale"> <p>This simplifies client-side code. Clients which care may distinguish between unsupported interfaces (e.g. this Connection does not support Avatars), and interfaces on which no information is known for these contacts (e.g. we don't know the avatar tokens of any of the contacts, so we omitted them all) by inspecting \\\\endhtmlonly \\\\link requestPropertyContactAttributeInterfaces() ContactAttributeInterfaces \\\\endlink \\\\htmlonly .</p> </div> <p>Attributes from the interface \\\\endhtmlonly ConnectionInterface \\\\htmlonly are always returned, and need not be requested explicitly.</p> <p>As well as returning cached information immediately, the connection MAY start asynchronous requests to obtain better values for the contact attributes. If better values are later obtained by this process, they will be indicated with the usual signals (such as \\\\endhtmlonly ConnectionInterfaceAliasingInterface::AliasesChanged() \\\\htmlonly ).</p> <div class="rationale"> For instance, an XMPP connection manager could download vCards in response to a request for \\\\endhtmlonly ConnectionInterfaceAliasingInterface \\\\htmlonly attributes. </div> \endhtmlonly |
hold | \htmlonly <p>If true, all handles that appear as keys in the result have been held on behalf of the calling process, as if by a call to \\\\endhtmlonly ConnectionInterface::HoldHandles() \\\\htmlonly . (If \\\\endhtmlonly \\\\link ConnectionInterface::requestPropertyHasImmortalHandles() ConnectionInterface::HasImmortalHandles \\\\endlink \\\\htmlonly is true, which SHOULD be the case in all new connection managers, this has no effect.)</p> <div class="rationale"> <p>For further round-trip avoidance.</p> </div> \endhtmlonly |
\htmlonly <p>A dictionary mapping the contact handles to contact attributes. If any of the requested handles are in fact invalid, they are simply omitted from this mapping. If contact attributes are not immediately known, the behaviour is defined by the interface; the attribute should either be omitted from the result or replaced with a default value.</p> <p>Each contact's attributes will always include at least the identifier that would be obtained by inspecting the handle (<code>org.freedesktop.Telepathy.Connection/contact-id</code>).</p> \endhtmlonly
|
slot |
Begins a call to the exported D-Bus method GetContactByID
on this object.
Adaptees should export this method as a Qt slot with the following signature: void getContactByID(const QString& identifier, const QStringList& interfaces, const Tp::Service::ConnectionInterfaceContactsAdaptor::GetContactByIDContextPtr &context);
Implementations should call MethodInvocationContext::setFinished (or setFinishedWithError accordingly) on the received context object once the method has finished processing.
Return any number of contact attributes for the given identifier. This is for a single identifier to make it simpler to use for the most common use case. For multiple contacts case, GetContactAttributes should be used.
identifier | An identifier representing a contact. |
interfaces | \htmlonly <p>A list of strings indicating which D-Bus interfaces the calling process is interested in. All supported attributes from these interfaces, whose values can be obtained without additional network activity, will be in the reply.</p> <p>See \\\\endhtmlonly GetContactAttributes() \\\\htmlonly for details.</p> \endhtmlonly |
attributes | Output parameter \htmlonly <p>All supported attributes of the contact on the given interfaces that can be returned without network round-trips. If contact attributes are not immediately known, the behaviour is defined by the interface; the attribute should either be omitted from the result or replaced with a default value.</p> <p>The contact's attributes will always include at least the identifier that would be obtained by inspecting the handle (<code>org.freedesktop.Telepathy.Connection/contact-id</code>).</p> \endhtmlonly |
\htmlonly <p>The contact's handle, as returned by \\\\endhtmlonly ConnectionInterface::RequestHandles() \\\\htmlonly </p> \endhtmlonly
TelepathyQt 0.9.8 |
Generated by
![]() |