Class
PurpleContact
Description [src]
final class Purple.Contact : GObject.Object {
/* No available fields */
}A representation of a user. Contacts are used everywhere you need to refer to a user. Be it a chat, an direct message, a file transfer, etc.
Instance methods
purple_contact_get_display_name
Gets the display name for contact. The display name is typically set by the
contact and is handled by the protocol plugin.
Available since: 3.0.0
purple_contact_set_avatar
Sets the avatar for contact to avatar. If avatar is NULL an existing
avatar will be removed.
Available since: 3.0.0
purple_contact_set_display_name
Sets the display name of contact to display_name.
Available since: 3.0.0
Properties
Purple.Contact:alias
The alias for this contact. This is controlled by the libpurple user and may be used by the protocol if it allows for aliasing.
Available since: 3.0.0
Purple.Contact:avatar
The avatar for this contact. This is typically controlled by the protocol and should only be read by others.
Available since: 3.0.0
Purple.Contact:display-name
The display name for this contact. This is generally set by the person the contact is representing and controlled via the protocol plugin.
Available since: 3.0.0
Purple.Contact:presence
The PurplePresence for this contact. This is typically
controlled by the protocol and should only be read by others.
Available since: 3.0.0
Purple.Contact:username
The username for this contact. In rare cases this can change, like when a user changes their “nick” on IRC which is their user name.
Available since: 3.0.0
Signals
Signals inherited from GObject (1)
GObject.Object::notify
The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.