Returns

tp_account_set_enabled_async ()

Requests an asynchronous set of the Enabled property of account
. When the
operation is finished, callback
will be called. You can then call
tp_account_set_enabled_finish() to get the result of the operation.

tp_account_update_parameters_async ()

Requests an asynchronous update of parameters of account
. When the
operation is finished, callback
will be called. You can then call
tp_account_update_parameters_finish() to get the result of the operation.

tp_account_set_display_name_async ()

Requests an asynchronous set of the DisplayName property of account
. When
the operation is finished, callback
will be called. You can then call
tp_account_set_display_name_finish() to get the result of the operation.

tp_account_set_icon_name_async ()

Requests an asynchronous set of the Icon property of account
. When
the operation is finished, callback
will be called. You can then call
tp_account_set_icon_name_finish() to get the result of the operation.

tp_account_set_service_async ()

Requests an asynchronous set of the Service property on self
. When
the operation is finished, callback
will be called. You can then call
tp_account_set_service_finish() to get the result of the operation.

tp_account_request_presence_async ()

Requests an asynchronous change of presence on account
. When the
operation is finished, callback
will be called. You can then call
tp_account_request_presence_finish() to get the result of the operation.

tp_account_set_automatic_presence_async ()

Requests an asynchronous change of account
's automatic presence. When the
operation is finished, callback
will be called. You can then call
tp_account_set_automatic_presence_finish() to get the result of the
operation.

tp_account_set_connect_automatically_async ()

Requests an asynchronous set of the ConnectAutomatically property of
account
. When the operation is finished, callback
will be called. You can
then call tp_account_set_display_name_finish() to get the result of the
operation.

Returns

tp_account_dup_detailed_error ()

If the account's connection is not connected, return the D-Bus error name
with which it last disconnected or failed to connect (in particular, this
is TP_ERROR_STR_CANCELLED if it was disconnected by a user request).
This is the same as “connection-error”.

tp_account_set_nickname_async ()

Requests an asynchronous change of the Nickname parameter on account
. When
the operation is finished, callback
will be called. You can then call
tp_account_set_nickname_finish() to get the result of the operation.

tp_account_set_avatar_async ()

Requests an asynchronous change of the Avatar parameter on self
. When
the operation is finished, callback
will be called. You can then call
tp_account_set_avatar_finish() to get the result of the operation.

scheme
should not be the primary URI scheme for the account's
protocol (for instance, "xmpp" for XMPP, or "sip" or "sips" for SIP),
since the account should be assumed to be useful for those schemes
regardless of the contents of the list.

Property Details

The “automatic-presence-type” property

When the account is put online automatically, for instance to make a
channel request or because network connectivity becomes available,
the automatic presence type, status and message will be copied to
their "requested" counterparts.

One can receive change notifications on this property by connecting
to the “notify” signal and using this property as the signal
detail. Change notifications for automatic-presence-type,
automatic-status and automatic-status-message are always emitted together,
so it is sufficient to connect to one of the notification signals.

The “automatic-status” property

One can receive change notifications on this property by connecting
to the “notify” signal and using this property as the signal
detail. Change notifications for automatic-presence-type,
automatic-status and automatic-status-message are always emitted together,
so it is sufficient to connect to one of the notification signals.

The “automatic-status-message” property

One can receive change notifications on this property by connecting
to the “notify” signal and using this property as the signal
detail. Change notifications for automatic-presence-type,
automatic-status and automatic-status-message are always emitted together,
so it is sufficient to connect to one of the notification signals.

One can receive change notifications on this property by connecting
to the “notify” signal and using this property as the signal
detail. If TP_ACCOUNT_FEATURE_CONNECTION has been prepared, this signal
will be delayed until the connection is ready.

The “current-presence-type” property

One can receive change notifications on this property by connecting
to the “notify” signal and using this property as the signal
detail. Change notifications for current-presence-type,
current-status and current-status-message are always emitted together,
so it is sufficient to connect to one of the notification signals.

The “current-status” property

One can receive change notifications on this property by connecting
to the “notify” signal and using this property as the signal
detail. Change notifications for current-presence-type,
current-status and current-status-message are always emitted together,
so it is sufficient to connect to one of the notification signals.

The “current-status-message” property

One can receive change notifications on this property by connecting
to the “notify” signal and using this property as the signal
detail. Change notifications for current-presence-type,
current-status and current-status-message are always emitted together,
so it is sufficient to connect to one of the notification signals.

The “requested-presence-type” property

Since 0.13.8,
one can receive change notifications on this property by connecting
to the “notify” signal and using this property as the signal
detail. Change notifications for requested-presence-type,
requested-status and requested-status-message are always emitted together,
so it is sufficient to connect to one of the notification signals.

The “requested-status” property

Since 0.13.8,
one can receive change notifications on this property by connecting
to the “notify” signal and using this property as the signal
detail. Change notifications for requested-presence-type,
requested-status and requested-status-message are always emitted together,
so it is sufficient to connect to one of the notification signals.

The “requested-status-message” property

Since 0.13.8,
one can receive change notifications on this property by connecting
to the “notify” signal and using this property as the signal
detail. Change notifications for requested-presence-type,
requested-status and requested-status-message are always emitted together,
so it is sufficient to connect to one of the notification signals.

The “service” property

A machine-readable name identifying a specific service to which this
account connects, or a copy of “protocol” if there is no more
specific service.

Well-known names for various services can be found in the Telepathy D-Bus
Interface Specification.

For instance, accounts for the "jabber" protocol should have the service
names "google_talk", "ovi_chat", "facebook" and "lj_talk" for accounts
that connect to Google Talk, Ovi Chat, Facebook and Livejournal,
respectively, and this property will be "jabber" for accounts that
connect to a generic Jabber server.

The “supersedes” property

The object paths of previously-active accounts superseded by this one.
For instance, this can be used in a logger to read old logs for an
account that has been migrated from one connection manager to another.

This is not guaranteed to have been retrieved until the
TP_ACCOUNT_FEATURE_CORE feature has been prepared; until then,
the value is NULL.

The “uri-schemes” property

If the TP_ACCOUNT_FEATURE_ADDRESSING feature has been prepared
successfully, a list of additional URI schemes for which this
account should be used if possible. Otherwise NULL.

For instance, a SIP or Skype account might have "tel" in this list if the
user would like to use that account to call phone numbers.

This list should not contain the primary URI scheme(s) for the account's
protocol (for instance, "xmpp" for XMPP, or "sip" or "sips" for SIP),
since it should be assumed to be useful for those schemes in any case.

The notify::uri-schemes signal cannot be relied on if the Account Manager
is Mission Control version 5.14.0 or older.