From e51587d4ba9cdfd3c1f97456a1d16e4c23018eaa Mon Sep 17 00:00:00 2001
From: Edric Milaret <edric.ladent-milaret@savoirfairelinux.com>
Date: Fri, 22 Jan 2016 13:41:14 -0500
Subject: [PATCH] peopleproxy: do no connect to rowMoved when using Qt
to rowsAboutToBeMoved too
I ve put a guard on the OS but the real problem is about Qt handling
layoutChanged signal and receiving a duplicate information
(and no longer valid) because of the rowsMoved forwarding necessary
to other platforms client (for now)
Change-Id: I30c2e89067e1fc16124d864f6df3406d678e40d5
Tuleap: #148
---
src/recentmodel.cpp | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/recentmodel.cpp b/src/recentmodel.cpp
index 9692510f..b0961e86 100644
--- a/src/recentmodel.cpp
+++ b/src/recentmodel.cpp
@@ -1090,8 +1090,10 @@ PeopleProxy::PeopleProxy(RecentModel* sourceModel)
// forward the rowsAboutToBeMoved and rowsMoved signals from the source model
// this is needed for the OSX and GNOME clients because they do not handle the layoutChanged
// signal which is emited by the QSortFilterProxyModel when rows are moved in the source model
+#ifndef Q_OS_WIN
connect(sourceModel, &QAbstractItemModel::rowsAboutToBeMoved, this, &PeopleProxy::slotRowsAboutToBeMoved);
connect(sourceModel, &QAbstractItemModel::rowsMoved, this, &PeopleProxy::slotRowsMoved);
+#endif
}
bool
--
GitLab