client: Don't send dataChanged() before actually changing the data
authorManuel Nickschas <sputnick@quassel-irc.org>
Wed, 29 Aug 2018 19:02:41 +0000 (21:02 +0200)
committerManuel Nickschas <sputnick@quassel-irc.org>
Mon, 3 Sep 2018 20:13:17 +0000 (22:13 +0200)
commitd1e7cc01969e8fb8cfc20a62a29176f417fc3507
treece19ab7fe8783c2edebe6753cd01e266f1038ab8
parent4c4fe2b514fc7ecf3186202d73b3b5ff8847763f
client: Don't send dataChanged() before actually changing the data

The PropertyMapItem didn't set a changed property before sending
the signal, so consumers synchronously reacting to dataChanged()
would still access the old value.

Not sure if this issue is the cause for some of the weird model
behavior we tend to see at times...
src/client/treemodel.cpp