1. 02 Jan, 2019 1 commit
  2. 12 Dec, 2018 1 commit
  3. 29 Nov, 2018 1 commit
    • Hugo Lefeuvre's avatar
      refresh popupmenu/chatview on account state change · 7e259ac4
      Hugo Lefeuvre authored
      Better UI reactivity on account state change:
      + Do not show audio and video call options in the conversationsview's
        popup menu when account is disabled (this doesn't make sense,
        account is not able to place a call)
      + Refresh popup menu on account state change (list of options
        has to be updated)
      + Refresh chatview on account state change (some elements of the
        chatview require update, e.g. message bar)
      + Fix broken display property update in hideControls()
      Misc code cleanup, add a few helpers to avoid code duplication.
      Change-Id: I212a47566bd65687e5ed61ec56087a4e1f3166bd
      Gitlab: #929Reviewed-by: Sébastien Blin's avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
  4. 09 May, 2018 1 commit
    • Hugo Lefeuvre's avatar
      popupmenu: fix menu for banned accounts · ef608eae
      Hugo Lefeuvre authored
      Currently the popup menu stays the same even if the account is banned
      which may be very confusing for the user (place call or block contact
      options are everything but meaningful in this case !).
      In this patch we implement a specific menu for banned accounts.
      In addition to that, we also force a chat view refresh when
      the filter is updated.
      This patch requires LRC side changes in order to work properly.
      Change-Id: Iea545fe5cf54520e7aba92c7a87a736bc6d71d27
      Reviewed-by: Sébastien Blin's avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
  5. 01 May, 2018 1 commit
    • Hugo Lefeuvre's avatar
      Refactoring of the accountContainer logic · 6f2ceb12
      Hugo Lefeuvre authored
       - RingMainWindow has an unique_ptr to an AccountContainer
       - each view / secondary class has its own *copy* of the account
         container pointer (given by ringmainwindow using
       - each time the reference to the struct Info is updated,
         accountContainer_ has to be reset()-ed and and the account
         container re-created by the RingMainWindow. This makes *all*
         copies of the account container pointer invalid (hence all
         view / secondary classes trying to access the account container
         before getting updated perform use-after-free / NULL pointer
       - These copies have to be manually updated ! (well, currently they
         are not updated at all)
       - RingMainWindow has a pointer to a struct Info from LRC.
       - Each view / secondary class has a pointer pointing to
         the struct Info pointer of RingMainWindow
       - Each time the reference to the struct Info is updated, the
         RingMainWindow updates its pointer. Since secondary classes and
         views hold a pointer to this pointer, they are automatically
         updated and there is no dangling pointer anymore.
      This requires no lrc side changes.
      Change-Id: I1329721920a3d42ad623f9fd7202b43700713eed
      Reviewed-by: Sébastien Blin's avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      Reviewed-by: Guillaume Roguez's avatarGuillaume Roguez <guillaume.roguez@savoirfairelinux.com>
  6. 12 Mar, 2018 1 commit
  7. 31 Jan, 2018 1 commit
  8. 14 Dec, 2017 1 commit
  9. 27 Nov, 2017 1 commit
  10. 02 Nov, 2017 1 commit
  11. 16 Oct, 2017 1 commit