diff options
author | Xavier Claessens <xavier.claessens@collabora.co.uk> | 2013-11-08 17:12:06 -0500 |
---|---|---|
committer | Xavier Claessens <xavier.claessens@collabora.co.uk> | 2013-11-11 10:59:58 -0500 |
commit | 6ebcb0f048fcf0107c6d7deb99a7f4717467561a (patch) | |
tree | ac13f23255fc177f0cf3c613ab695091e7eb54fe /mission-control-plugins | |
parent | 8171d9e5bc8d4f47a36844afab0a6063b1958004 (diff) |
Make sure to not delete() nor commit() and account deleted from storage
If it is the storage plugin informing MC that the account has been
deleted, we can assume that the storage will already take care of
removing all information.
Diffstat (limited to 'mission-control-plugins')
-rw-r--r-- | mission-control-plugins/account-storage.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/mission-control-plugins/account-storage.c b/mission-control-plugins/account-storage.c index a5b89f0c..dd478d88 100644 --- a/mission-control-plugins/account-storage.c +++ b/mission-control-plugins/account-storage.c @@ -261,8 +261,11 @@ class_init (gpointer klass, * Emitted if an external entity deletes an account * in the backend the emitting plugin handles. * - * Should not be fired until mcp_account_storage_ready() has been called + * Should not be fired until mcp_account_storage_ready() has been called. * + * mcp_account_storage_commit() and mcp_account_storage_delete() won't be + * called for this account, it is assumed that the storage backend already + * deleted all the related information. */ signals[DELETED] = g_signal_new ("deleted", type, G_SIGNAL_RUN_LAST, 0, NULL, NULL, |