Emitted when SMTP connection is established and login was successful.
Emitted when IMAP connection is established and login was successful.
Emitted when a message was successfully sent to the SMTP server.
Emitted when an IMAP message has been marked as deleted
Emitted when an IMAP message has been moved
Emitted before going into IDLE on the Inbox folder.
Emitted when an new file in the $BLOBDIR was created
Emitted when an file in the $BLOBDIR was deleted
The library-user should write a warning string to the log.
This event should not be reported to the end-user using a popup or something like that.
The library-user should report an error to the end-user.
As most things are asynchronous, things may go wrong at any time and the user should not be disturbed by a dialog or so. Instead, use a bubble or so.
However, for ongoing processes (eg. configure()) or for functions that are expected to fail (eg. autocryptContinueKeyTransfer()) it might be better to delay showing these events until the function has really failed (returned false). It should be sufficient to report only the last error in a message box then.
An action cannot be performed because the user is not in the group. Reported eg. after a call to setChatName(), setChatProfileImage(), addContactToChat(), removeContactFromChat(), and messages sending functions.
Messages or chats changed. One or more messages or chats changed for various reasons in the database:
Reactions for the message changed.
A reaction to one's own sent message received. Typically, the UI will show a notification for that.
In addition to this event, ReactionsChanged is emitted.
Incoming webxdc info or summary update, should be notified.
There is a fresh message. Typically, the user will show a notification when receiving this message.
There is no extra #DC_EVENT_MSGS_CHANGED event sent together with this event.
Downloading a bunch of messages just finished. This is an event to allow the UI to only show one notification per message bunch, instead of cluttering the user with many notifications.
Messages were seen or noticed. chat id is always set.
A single message is sent successfully. State changed from DC_STATE_OUT_PENDING to
DC_STATE_OUT_DELIVERED, see Message.state
.
A single message could not be sent. State changed from DC_STATE_OUT_PENDING or DC_STATE_OUT_DELIVERED to
DC_STATE_OUT_FAILED, see Message.state
.
A single message is read by the receiver. State changed from DC_STATE_OUT_DELIVERED to
DC_STATE_OUT_MDN_RCVD, see Message.state
.
A single message was deleted.
This event means that the message will no longer appear in the messagelist. UI should remove the message from the messagelist in response to this event if the message is currently displayed.
The message may have been explicitly deleted by the user or expired. Internally the message may have been removed from the database, moved to the trash chat or hidden.
This event does not indicate the message deletion from the server.
Chat changed. The name or the image of a chat group was changed or members were added or removed. Or the verify state of a chat has changed. See setChatName(), setChatProfileImage(), addContactToChat() and removeContactFromChat().
This event does not include ephemeral timer modification, which is a separate event.
Chat ephemeral timer changed.
Chat deleted.
Contact(s) created, renamed, blocked or deleted.
Location of one or more contact has changed.
Inform about the configuration progress started by configure().
Progress comment or error, something to display to the user.
Progress.
0=error, 1-999=progress in permille, 1000=success and done
Inform about the import/export progress started by imex().
0=error, 1-999=progress in permille, 1000=success and done
A file has been exported. A file has been written by imex(). This event may be sent multiple times by a single call to imex().
A typical purpose for a handler of this event may be to make the file public to some system services.
Progress information of a secure-join handshake from the view of the inviter (Alice, the person who shows the QR code).
These events are typically sent after a joiner has scanned the QR code generated by getChatSecurejoinQrCodeSvg().
ID of the contact that wants to join.
Progress as: 300=vg-/vc-request received, typically shown as "bob@addr joins". 600=vg-/vc-request-with-auth received, vg-member-added/vc-contact-confirm sent, typically shown as "bob@addr verified". 800=contact added to chat, shown as "bob@addr securely joined GROUP". Only for the verified-group-protocol. 1000=Protocol finished for this contact.
Progress information of a secure-join handshake from the view of the joiner (Bob, the person who scans the QR code). The events are typically sent while secureJoin(), which may take some time, is executed.
The connectivity to the server changed. This means that you should refresh the connectivity view and possibly the connectivtiy HTML; see getConnectivity() and getConnectivityHtml() for details.
Deprecated by ConfigSynced
.
A multi-device synced config value changed. Maybe the app needs to refresh smth. For uniformity this is emitted on the source device too. The value isn't here, otherwise it would be logged which might not be good for privacy.
Configuration key.
Data received over an ephemeral peer channel.
Advertisement received over an ephemeral peer channel. This can be used by bots to initiate peer-to-peer communication from their side.
Inform that a message containing a webxdc instance has been deleted
Tells that the Background fetch was completed (or timed out). This event acts as a marker, when you reach this event you can be sure that all events emitted during the background fetch were processed.
This event is only emitted by the account manager
Inform that set of chats or the order of the chats in the chatlist has changed.
Sometimes this is emitted together with UIChatlistItemChanged
.
Inform that a single chat list item changed and needs to be rerendered.
If chat_id
is set to None, then all currently visible chats need to be rerendered, and all not-visible items need to be cleared from cache if the UI has a cache.
Inform that the list of accounts has changed (an account removed or added or (not yet implemented) the account order changes)
This event is only emitted by the account manager
Inform that an account property that might be shown in the account list changed, namely:
This event is emitted from the account whose property changed.
Inform than some events have been skipped due to event channel overflow.
Number of events skipped.
The library-user may write an informational string to the log.
This event should not be reported to the end-user using a popup or something like that.