Skip to content
Snippets Groups Projects
Select Git revision
  • 463b45ecaeaaedda2ac9efb1bb6a40e65beaf6dd
  • master default protected
  • release/202005
  • release/202001
  • release/201912
  • release/201911
  • release/releaseWindowsTestOne
  • release/releaseTest
  • release/releaseWindowsTest
  • release/windowsReleaseTest
  • release/201910
  • release/qt/201910
  • release/windows-test/201910
  • release/201908
  • release/201906
  • release/201905
  • release/201904
  • release/201903
  • release/201902
  • release/201901
  • release/201812
  • 1.0.0
  • 0.3.0
  • 0.2.1
  • 0.2.0
  • 0.1.0
26 results

jami-libclient

  • Clone with SSH
  • Clone with HTTPS
    • user avatar
    RecentModel: fix ContactMethod node removal
    Stepan Salenikovich authored 
    This fixes one particular instance of "contact duplication" in the
RecentModel. When we had a call from a peer incoming for the very
first time, a ContactMethod ndoe was first being created. Then we
received the profile from the peer, and so a Person node was created.
However, the contactChanged signal could be called before the Person
node is created; in this case the ContactMethod node was not being
removed and the result was a duplication of the the same contact
twice in the RecentModel: once as a CM and once as a Person.

Calling slotLastUsedTimeChanged() on the new Person ensures that
the Person node is created.

We also call slotContactChanged() from slotPersonAdded() to reduce
code duplication.

Change-Id: Ia9b49ab939a017052cccc69f8d72df5db0aef41d
    463b45ec
    History
    user avatar 463b45ec
    History
    Name Last commit Last update
    .tx
    cmake
    share/ring/bootstrap
    src
    translations
    .gitignore
    .gitreview
    CMakeLists.txt
    COPYING
    INSTALL
    README.md