Skip to content
Snippets Groups Projects
Select Git revision
  • 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
25 results

contactmodel.h

  • Hugo Lefeuvre's avatar
    f57ea000
    contactmodel: introduce bannedStatusChanged signal · f57ea000
    Hugo Lefeuvre authored and Sébastien Blin's avatar Sébastien Blin committed
    
    cb08d760 introduced a new banned contacts logic to the contact model,
    which allows to manage banned contacts without using the old lrc.
    While this patch is fully functional, the problem of how exactly the
    client is notified about a banning / unbanning operation is still
    unclear: currently the only way the client gets notified is via the
    refreshFilter() operation. This is enough for managing banned
    contacts in the smart list, but not in the banned contacts view.
    
    In order to addres this problem we introduce a new signal,
    bannedStatusChanged, which allows the client to be notified when a
    contact is banned or unbanned.
    
    Change-Id: I2ea845e0fe311048479777504b74885cb931aa13
    Reviewed-by: default avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
    f57ea000
    History
    contactmodel: introduce bannedStatusChanged signal
    Hugo Lefeuvre authored and Sébastien Blin's avatar Sébastien Blin committed
    
    cb08d760 introduced a new banned contacts logic to the contact model,
    which allows to manage banned contacts without using the old lrc.
    While this patch is fully functional, the problem of how exactly the
    client is notified about a banning / unbanning operation is still
    unclear: currently the only way the client gets notified is via the
    refreshFilter() operation. This is enough for managing banned
    contacts in the smart list, but not in the banned contacts view.
    
    In order to addres this problem we introduce a new signal,
    bannedStatusChanged, which allows the client to be notified when a
    contact is banned or unbanned.
    
    Change-Id: I2ea845e0fe311048479777504b74885cb931aa13
    Reviewed-by: default avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
Code owners
Assign users and groups as approvers for specific file changes. Learn more.