Class
CamelVeeStore
Instance methods
camel_vee_store_note_subfolder_unused
This is a counter part of camel_vee_store_note_subfolder_used(). Once
the subfolder
is claimed to be not used by all folders its message infos
are removed from the Unmatched folder.
since: 3.6
camel_vee_store_note_subfolder_used
Notes that the subfolder
is used by used_by
folder, which
is used to determine what folders will be included in
the Unmatched folders.
since: 3.6
camel_vee_store_note_vuid_unused
A counter part of camel_vee_store_note_vuid_used(). Once the unused_by
claims the mi_data
is not used by it anymore, and neither any other
virtual folder is using it, then the Unmatched folder will have it added.
since: 3.6
camel_vee_store_note_vuid_used
Notes the mi_data
is used by the used_by
virtual folder, which
removes it from the Unmatched folder, if not used anywhere else.
since: 3.6
camel_vee_store_rebuild_unmatched_folder
Let’s the vstore
know to rebuild the Unmatched folder. This is done
as a separate job, when the cancellable
is NULL
, otherwise it’s run synchronously.
since: 3.6
camel_vee_store_set_unmatched_enabled
Sets whether the Unmatched folder processing is enabled.
since: 3.6
Methods inherited from CamelStore (46)
Please see CamelStore for a full list of methods.
Methods inherited from CamelService (32)
Please see CamelService for a full list of methods.
Methods inherited from CamelObject (4)
camel_object_get_state_filename
Returns the name of the file in which persistent property values for
object
are stored. The file is used by camel_object_state_write()
and camel_object_state_read()
to save and restore object state.
since: 2.32
camel_object_set_state_filename
Sets the name of the file in which persistent property values for
object
are stored. The file is used by camel_object_state_write()
and camel_object_state_read()
to save and restore object state.
since: 2.32
camel_object_state_read
Read persistent object state from CamelObject:state-filename
.
camel_object_state_write
Write persistent object state CamelObject:state-filename
.
Methods inherited from GInitable (1)
Properties
Properties inherited from CamelService (8)
Camel.Service:connection-status
Camel.Service:display-name
Camel.Service:password
Camel.Service:provider
Camel.Service:proxy-resolver
Camel.Service:session
Camel.Service:settings
Camel.Service:uid
Properties inherited from CamelObject (1)
Camel.Object:state-filename
The file in which to store persistent property values for this instance.
Signals
Signals inherited from CamelStore (5)
CamelStore::folder-created
CamelStore::folder-deleted
CamelStore::folder-info-stale
This signal indicates significant changes have occurred to
the folder hierarchy of store
, and that previously fetched
CamelFolderInfo
data should be considered stale.
CamelStore::folder-opened
CamelStore::folder-renamed
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.