Class
CamelFolderThread
Description [src]
final class Camel.FolderThread : GObject.Object
{
/* No available fields */
}Message threading / conversation grouping.
CamelFolderThread computes conversation threads from a list of messages
in a folder, based on the In-Reply-To and References headers as described
by Jamie Zawinski’s threading algorithm (used by Netscape 3 Mail).
Because threading operates on pre-computed hashes from CamelMessageInfo
rather than parsing raw message content, it is very fast.
The result is a tree of CamelFolderThreadNode structures accessible via the tree field of the CamelFolderThread object. Each node carries a
pointer to its CamelMessageInfo and links to its parent, next sibling,
and first child, making it straightforward to build a tree-view model.
An optional subject-based fallback algorithm can be enabled (by passing
thread_subject = TRUE to camel_folder_thread_new()) to find conversation
parts when In-Reply-To / References headers are absent, by matching
“Re: ” prefixes on subject lines.
Constructors
camel_folder_thread_new_items
Creates a folder tree of the provided items, which can be accessed only
by the provided functions. The get_date_sent_func and the get_date_received_func
can be NULL only when the flags does not contain CAMEL_FOLDER_THREAD_FLAG_SORT.
since: 3.58
Signals
Signals inherited from GObject (1)
GObject::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.