From 8793d7c5a259261fcafc7ca5c4604b91215458d3 Mon Sep 17 00:00:00 2001
From: Kateryna Kostiuk <kateryna.kostiuk@savoirfairelinux.com>
Date: Wed, 21 Jun 2017 12:36:10 -0400
Subject: [PATCH] BannedContactModel: check if entry exists
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sometimes contact method could be added to BannedContactModel twice:
during creating model and from accountModel when receiving
slotContactRemoved.(it happens if account does not have bannedContactModel
yet). This patch fix it by checking if ContactMethod already exists in the
banned contact list.
Change-Id: I514e0301bbc07378ef9f9a5c345db5b49c8e23e0
Reviewed-by: Anthony Léonard <anthony.leonard@savoirfairelinux.com>
---
src/bannedcontactmodel.cpp | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/bannedcontactmodel.cpp b/src/bannedcontactmodel.cpp
index 70aa6c0f..af2b58ee 100644
--- a/src/bannedcontactmodel.cpp
+++ b/src/bannedcontactmodel.cpp
@@ -137,6 +137,8 @@ BannedContactModel::columnCount( const QModelIndex& parent ) const
void
BannedContactModel::add(ContactMethod* cm)
{
+ if (d_ptr->m_lBanned.contains(cm))
+ return;
beginInsertRows(QModelIndex(),d_ptr->m_lBanned.size(),d_ptr->m_lBanned.size());
d_ptr->m_lBanned << cm;
endInsertRows();
--
GitLab