diff options
| author | Kitsune Ral <Kitsune-Ral@users.sf.net> | 2016-05-02 22:26:06 +0900 |
|---|---|---|
| committer | Kitsune Ral <Kitsune-Ral@users.sf.net> | 2016-05-02 23:05:59 +0900 |
| commit | 9a415111fefd0d21f8b4abbbe9af9066d78c971b (patch) | |
| tree | 737052a0675b5ecce7c3d2902f2278400f13885e /kcoreaddons | |
| parent | b36a9f32b1fcdce404e9a0a8cb780ba2ab89c24b (diff) | |
| download | libquotient-9a415111fefd0d21f8b4abbbe9af9066d78c971b.tar.gz libquotient-9a415111fefd0d21f8b4abbbe9af9066d78c971b.zip | |
Actually connect User::nameChanged to Room; make a new Room::memberRenamed signal, which clients should use in the room context.
Processing changes of user displaynames is tricky: we have to not only deal with the currently renamed user but also with its past and new namesakes which might change representation due to that renaming. So in the worst case a single User::nameChanged signal may lead to three Room::memberRenamed references (and 3 user displaynames updated in the UI, respectively). And the newly added users should be taken care of in a similar manner, of course.
Diffstat (limited to 'kcoreaddons')
0 files changed, 0 insertions, 0 deletions