#include <TelepathyQt4/Client/Channel>
Public Slots | |
QDBusPendingReply< QString > | SendMessage (const Telepathy::MessagePartList &message, uint flags) |
QDBusPendingReply < Telepathy::MessagePartContentMap > | GetPendingMessageContent (uint messageID, const Telepathy::UIntList &parts) |
Signals | |
void | MessageSent (const Telepathy::MessagePartList &content, uint flags, const QString &messageToken) |
void | PendingMessagesRemoved (const Telepathy::UIntList &messageIDs) |
void | MessageReceived (const Telepathy::MessagePartList &message) |
Public Member Functions | |
ChannelInterfaceMessagesInterface (const QString &serviceName, const QString &objectPath, QObject *parent=0) | |
ChannelInterfaceMessagesInterface (const QDBusConnection &connection, const QString &serviceName, const QString &objectPath, QObject *parent=0) | |
ChannelInterfaceMessagesInterface (Telepathy::Client::DBusProxy *proxy) | |
ChannelInterfaceMessagesInterface (const Telepathy::Client::ChannelInterface &mainInterface) | |
ChannelInterfaceMessagesInterface (const Telepathy::Client::ChannelInterface &mainInterface, QObject *parent) | |
QStringList | SupportedContentTypes () const TELEPATHY_GNUC_DEPRECATED |
uint | MessagePartSupportFlags () const TELEPATHY_GNUC_DEPRECATED |
Telepathy::MessagePartListList | PendingMessages () const TELEPATHY_GNUC_DEPRECATED |
uint | DeliveryReportingSupport () const TELEPATHY_GNUC_DEPRECATED |
Static Public Member Functions | |
static const char * | staticInterfaceName () |
Protected Member Functions | |
virtual void | invalidate (Telepathy::Client::DBusProxy *, const QString &, const QString &) |
Properties | |
QStringList | SupportedContentTypes |
uint | MessagePartSupportFlags |
Telepathy::MessagePartListList | PendingMessages |
uint | DeliveryReportingSupport |
Telepathy::Client::ChannelInterfaceMessagesInterface::ChannelInterfaceMessagesInterface | ( | const QString & | serviceName, | |
const QString & | objectPath, | |||
QObject * | parent = 0 | |||
) |
Creates a ChannelInterfaceMessagesInterface associated with the given object on the session bus.
serviceName | Name of the service the object is on. | |
objectPath | Path to the object on the service. | |
parent | Passed to the parent class constructor. |
Telepathy::Client::ChannelInterfaceMessagesInterface::ChannelInterfaceMessagesInterface | ( | const QDBusConnection & | connection, | |
const QString & | serviceName, | |||
const QString & | objectPath, | |||
QObject * | parent = 0 | |||
) |
Creates a ChannelInterfaceMessagesInterface associated with the given object on the given bus.
connection | The bus via which the object can be reached. | |
serviceName | Name of the service the object is on. | |
objectPath | Path to the object on the service. | |
parent | Passed to the parent class constructor. |
Telepathy::Client::ChannelInterfaceMessagesInterface::ChannelInterfaceMessagesInterface | ( | Telepathy::Client::DBusProxy * | proxy | ) |
Creates a ChannelInterfaceMessagesInterface associated with the same object as the given proxy.
proxy | The proxy to use. It will also be the QObject::parent() for this object. |
Telepathy::Client::ChannelInterfaceMessagesInterface::ChannelInterfaceMessagesInterface | ( | const Telepathy::Client::ChannelInterface & | mainInterface | ) | [explicit] |
Creates a ChannelInterfaceMessagesInterface associated with the same object as the given proxy. Additionally, the created proxy will have the same parent as the given proxy.
mainInterface | The proxy to use. |
Telepathy::Client::ChannelInterfaceMessagesInterface::ChannelInterfaceMessagesInterface | ( | const Telepathy::Client::ChannelInterface & | mainInterface, | |
QObject * | parent | |||
) |
Creates a ChannelInterfaceMessagesInterface associated with the same object as the given proxy. However, a different parent object can be specified.
mainInterface | The proxy to use. | |
parent | Passed to the parent class constructor. |
uint Telepathy::Client::ChannelInterfaceMessagesInterface::DeliveryReportingSupport | ( | ) | const [inline] |
Getter for the remote object property "DeliveryReportingSupport".
Don't use this: it blocks the main loop.
QDBusPendingReply<Telepathy::MessagePartContentMap> Telepathy::Client::ChannelInterfaceMessagesInterface::GetPendingMessageContent | ( | uint | messageID, | |
const Telepathy::UIntList & | parts | |||
) | [inline, slot] |
Begins a call to the D-Bus method "GetPendingMessageContent" on the remote object.
Retrieve the content of one or more parts of a pending message. Note that this function may take a considerable amount of time to return if the part's 'needs-retrieval' flag is true; consider extending the default D-Bus method call timeout. Additional API is likely to be added in future, to stream large message parts.
messageID | The ID of a pending message | |
parts | The desired entries in the array of message parts, identified by their position. The "headers" part (which is not a valid argument to this method) is considered to be part 0, so the valid part numbers start at 1 (for the second Message_Part). |
The content of the requested parts. The keys in this mapping are positions in the array of message parts; the values are either of type 's' or 'ay' (UTF-8 text string, or byte array), following the same rules as for the value of the 'content' key in the <tp:type>Message_Part</tp:type> mappings.
If the one of the requested part numbers was greater than zero but referred to a part that had no content (i.e. it had no 'content-type' key or no 'content' key), it is simply omitted from this mapping; this is not considered to be an error condition.
References Telepathy::Client::AbstractInterface::invalidationMessage(), and Telepathy::Client::AbstractInterface::invalidationReason().
virtual void Telepathy::Client::ChannelInterfaceMessagesInterface::invalidate | ( | Telepathy::Client::DBusProxy * | , | |
const QString & | , | |||
const QString & | ||||
) | [protected, virtual] |
Reimplemented from Telepathy::Client::AbstractInterface.
uint Telepathy::Client::ChannelInterfaceMessagesInterface::MessagePartSupportFlags | ( | ) | const [inline] |
Getter for the remote object property "MessagePartSupportFlags".
Don't use this: it blocks the main loop.
void Telepathy::Client::ChannelInterfaceMessagesInterface::MessageReceived | ( | const Telepathy::MessagePartList & | message | ) | [signal] |
Represents the signal "MessageReceived" on the remote object.
Signals that a message has been received and added to the pending messages queue. This MUST be emitted exactly once per emission of the Received signal on the Text interface. The double signal-emission provides compatibility with older clients. Clients supporting Messages should listen for Messages.MessageReceived only (if the channel has the Messages interface) or Text.Received only (otherwise).
message | The message content, including any attachments or alternatives |
void Telepathy::Client::ChannelInterfaceMessagesInterface::MessageSent | ( | const Telepathy::MessagePartList & | content, | |
uint | flags, | |||
const QString & | messageToken | |||
) | [signal] |
Represents the signal "MessageSent" on the remote object.
Signals that a message has been submitted for sending. This MUST be emitted exactly once per emission of the <tp:dbus-ref namespace="org.freedesktop.Telepathy.Channel.Type.Text">Sent</tp:dbus-ref> signal on the Text interface.
<tp:rationale>
This signal allows a process that is not the caller of SendMessage to log sent messages. The double signal-emission provides compatibility with older clients. Clients supporting Messages should listen for Messages.MessageSent only (if the channel has the Messages interface) or Text.Sent only (otherwise). </tp:rationale>
content |
If the connection manager can predict that the message will be altered during transmission, this argument SHOULD reflect what other contacts will receive, rather than being a copy of the argument to SendMessage (if the message is truncated, formatting or alternatives are dropped, etc., then the edited version SHOULD appear in this signal).
flags | Flags affecting how the message was sent. The flags might be a subset of those passed to SendMessage if the caller requested unsupported flags. | |
messageToken | An opaque token used to match any incoming delivery or failure reports against this message, or an empty string if the message is not readily identifiable. |
Telepathy::MessagePartListList Telepathy::Client::ChannelInterfaceMessagesInterface::PendingMessages | ( | ) | const [inline] |
Getter for the remote object property "PendingMessages".
Don't use this: it blocks the main loop.
void Telepathy::Client::ChannelInterfaceMessagesInterface::PendingMessagesRemoved | ( | const Telepathy::UIntList & | messageIDs | ) | [signal] |
Represents the signal "PendingMessagesRemoved" on the remote object.
The messages with the given IDs have been removed from the PendingMessages list. Clients SHOULD NOT attempt to acknowledge those messages. This completes change notification for the PendingMessages property (previously, there was change notification when pending messages were added, but not when they were removed).
messageIDs | The messages that have been removed from the pending message list. |
QDBusPendingReply<QString> Telepathy::Client::ChannelInterfaceMessagesInterface::SendMessage | ( | const Telepathy::MessagePartList & | message, | |
uint | flags | |||
) | [inline, slot] |
Begins a call to the D-Bus method "SendMessage" on the remote object.
Submit a message to the server for sending. If this method returns successfully, the message has been submitted to the server and the <tp:member-ref>MessageSent</tp:member-ref> signal is emitted. A corresponding <tp:dbus-ref namespace="org.freedesktop.Telepathy.Channel.Type.Text">Sent</tp:dbus-ref> signal on the Text interface MUST also be emitted.
This method MUST return before the MessageSent signal is emitted.
<tp:rationale>
This means that the process sending the message is the first to see the <tp:type>Sent_Message_Token</tp:type>, and can relate the message to the corresponding <tp:member-ref>MessageSent</tp:member-ref> signal by comparing message tokens (if supported by the protocol). </tp:rationale>
If this method fails, message submission to the server has failed and no signal on this interface (or the Text interface) is emitted.
message | The message content, including any attachments or alternatives | |
flags | Flags affecting how the message is sent. |
References Telepathy::Client::AbstractInterface::invalidationMessage(), and Telepathy::Client::AbstractInterface::invalidationReason().
static const char* Telepathy::Client::ChannelInterfaceMessagesInterface::staticInterfaceName | ( | ) | [inline, static] |
Returns the name of the interface "org.freedesktop.Telepathy.Channel.Interface.Messages", which this class represents.
QStringList Telepathy::Client::ChannelInterfaceMessagesInterface::SupportedContentTypes | ( | ) | const [inline] |
Getter for the remote object property "SupportedContentTypes".
Don't use this: it blocks the main loop.
uint Telepathy::Client::ChannelInterfaceMessagesInterface::DeliveryReportingSupport [read] |
Represents property "DeliveryReportingSupport" on the remote object.
A bitfield indicating features supported by this channel.
uint Telepathy::Client::ChannelInterfaceMessagesInterface::MessagePartSupportFlags [read] |
Represents property "MessagePartSupportFlags" on the remote object.
Flags indicating the level of support for message parts on this channel.
Telepathy::MessagePartListList Telepathy::Client::ChannelInterfaceMessagesInterface::PendingMessages [read] |
Represents property "PendingMessages" on the remote object.
A list of incoming messages that have neither been acknowledged nor rejected. This list is a more detailed version of the one returned by Text.ListPendingMessages, and contains the same messages, uniquely identified by the same pending message IDs. Its items can be removed using Text.AcknowledgePendingMessages.
QStringList Telepathy::Client::ChannelInterfaceMessagesInterface::SupportedContentTypes [read] |
Represents property "SupportedContentTypes" on the remote object.
A list of MIME types supported by this channel, with more preferred MIME types appearing earlier in the list. The list MAY include "*/*" to indicate that attachments with arbitrary MIME types can be sent. This list MUST NOT be empty, since all Messages implementations MUST accept messages containing a single "text/plain" part.
Some examples of how this property interacts with the <tp:member-ref>MessagePartSupportFlags</tp:member-ref>: