1. 29 Apr, 2021 1 commit
  2. 27 Apr, 2021 1 commit
  3. 22 Apr, 2021 1 commit
    • Damien Caliste's avatar
      [nemo-qml-plugin-calendar] Ensure that deleted events are in memory · 694e8cce
      Damien Caliste authored
      When running several delete actions in a row from the calendarapi object,
      the storage is reloaded between each delete call. This results in
      the memory calendar to be emptied after each delete action. When the
      next delete action is arriving, the event to delete is not in memory
      anymore and the deletion is aborted.
      694e8cce
  4. 09 Mar, 2021 1 commit
  5. 29 Jan, 2021 1 commit
  6. 28 Jan, 2021 2 commits
  7. 25 Jan, 2021 1 commit
  8. 20 Jan, 2021 1 commit
  9. 15 Jan, 2021 1 commit
    • Chris Adams's avatar
      [nemo-qml-plugin-calendar] Use mKCal::Notebook color as canonical color. Contributes to JB#51280 · 7ccf9e49
      Chris Adams authored
      Previously, the canonical color used for display purposes in the
      jolla-calendar application for a particular notebook was stored
      in a QSettings .ini file.
      
      That allowed the user to define a color for a calendar locally, without
      perturbing the color specified on the server.  However, it also meant
      that the semantics of color selection were not easily discoverable,
      and further, that synchronisation of the color selection would never
      be performed.
      
      This commit ensures that the synced color will be used as the color
      displayed in the application, and that the color selection will be
      stored into the notebook in the database.
      
      Finally, it ensures that if no color is set, a default color is chosen
      and stored into the notebook, to avoid the possibility that the color
      of the primary notebook can change between reboots.
      7ccf9e49
  10. 13 Jan, 2021 1 commit
  11. 12 Jan, 2021 2 commits
  12. 11 Jan, 2021 1 commit
  13. 05 Jan, 2021 1 commit
  14. 23 Dec, 2020 1 commit
  15. 20 Dec, 2020 1 commit
  16. 16 Dec, 2020 2 commits
  17. 24 Nov, 2020 1 commit
  18. 16 Nov, 2020 1 commit
  19. 15 Sep, 2020 1 commit
  20. 25 Aug, 2020 2 commits
  21. 17 Aug, 2020 1 commit
  22. 16 Jun, 2020 1 commit
  23. 09 Jun, 2020 3 commits
  24. 06 Jun, 2020 1 commit
  25. 04 Jun, 2020 3 commits
  26. 14 May, 2020 1 commit
  27. 01 Apr, 2020 1 commit
  28. 27 Mar, 2020 1 commit
    • chriadam's avatar
      [nemo-qml-plugin-calendar] Prevent flicker of attendees. Contributes to JB#32993 · 1ba0729c
      chriadam authored
      The CalendarWorker observes storageModified() signals sent from mkcal.
      In mkcal side, when storageModified() is emitted, loaded ranges are
      invalidated and must be re-loaded.  Thus, when CalendarWorker observes
      the storageModified() signal, it tells the CalendarManager that it
      needs to rebuild its required ranges (from connected AgendaModel
      and currently active EventQuery instances).  The CalendarManager
      then asks the CalendarWorker to load instances within that range
      into the calendar from storage.
      
      If an EventQuery is refreshed as part of this process, it previously
      always emitted attendeesChanged() even if the data in the backend
      remained the same.  This commit ensures that we load the data from
      the backend, and compare it to the currently cached data, and only
      emit attendeesChanged() if they are indeed different.
      
      Finally, it guards against a race condition case where if multiple
      storageModified() signals are received in sequence, the some attempts
      to load the attendees may fail due to the storage having invalidated
      its loaded ranges.  In this case, the results we receive back will
      be invalid, and should be ignored (and in this case, the data for
      the event will be reloaded again, as triggered by storageModified()).
      1ba0729c
  29. 11 Mar, 2020 1 commit
  30. 05 Mar, 2020 1 commit
  31. 25 Feb, 2020 1 commit
  32. 10 Feb, 2020 1 commit