1. 16 Nov, 2020 1 commit
  2. 09 Nov, 2020 1 commit
  3. 08 Nov, 2020 1 commit
  4. 07 Nov, 2020 1 commit
  5. 05 Nov, 2020 1 commit
    • Damien Caliste's avatar
      Raise ambiguity in ICalFormat::toString() in tests · 8af20c62
      Damien Caliste authored
      For some reason, CI had trouble to compile toString(calendar),
      making toString(KCalendarCore::MemoryCalendar::Ptr&) and
      toString(const KCalendarCore::Incidence::Ptr&) ambiguous.
      Add the optional argument to the first call so the ambiguity
      is raised.
      8af20c62
  6. 04 Nov, 2020 1 commit
  7. 12 Oct, 2020 1 commit
  8. 10 Oct, 2020 1 commit
  9. 04 Oct, 2020 1 commit
  10. 17 Sep, 2020 2 commits
  11. 12 Sep, 2020 1 commit
  12. 06 Sep, 2020 1 commit
  13. 03 Sep, 2020 2 commits
  14. 17 Aug, 2020 1 commit
  15. 08 Aug, 2020 1 commit
  16. 01 Aug, 2020 1 commit
  17. 13 Jul, 2020 1 commit
  18. 12 Jul, 2020 1 commit
  19. 09 Jul, 2020 1 commit
    • Adriaan de Groot's avatar
      Fix unittests on FreeBSD. · f84e6a9a
      Adriaan de Groot authored
      - The "short form" timezone "GMT" does not always exist on FreeBSD. Use short form "UTC" instead.
      - While here, add a little test that the named timezone is valid.
      - Make tests a little more explicit as to what they're testing.
      f84e6a9a
  20. 04 Jul, 2020 1 commit
  21. 01 Jul, 2020 1 commit
  22. 13 Jun, 2020 1 commit
  23. 12 Jun, 2020 4 commits
  24. 10 Jun, 2020 3 commits
    • Glen Ditchfield's avatar
      Correct icon names for recurring to-dos · d5968e55
      Glen Ditchfield authored
      `Todo::iconName()` compares a "recurrenceId" to the due date of the current
      occurrence of the todo to decide whether the specified occurrence has been
      completed.
       * To-dos do not have to have a due date.  In that case the comparison
         fails, and `"view-calendar-tasks"` is always returned.
       * RFC 2445/RFC 5545 say that a recurrence ID is the start date of an
         occurrence, and KOrganizer's Agenda view passes start dates to
        `iconName()`.  In that case `iconName()` incorrectly returns
        `"task-complete"` for the first occurrence of a never-completed to-do.
      
      Comparing the recurrence ID to the start date of the current occurrence
      fixes the problems.
      d5968e55
    • Glen Ditchfield's avatar
      Fix serialization of recurring to-do's start date · dc7b1865
      Glen Ditchfield authored
      KCalendarCore uses Todo::Private::mDtRecurrence to hold the start date
      and time of the next uncompleted occurrance of a recurring Todo, and
      deserializes it from the X-KDE-LIBKCAL-DTRECURRENCE property of iCalendar
      files.  However, ICalFormatImpl::writeTodo() serializes dtDue() into that
      property, not dtStart().
      
      When KOrganizer creates a new recurring to-do, it serializes the to-do,
      then deserializes it to populate the To-Do List view, so the view shows
      an incorrect start date (and an incorrect due date, which is calculated
      from the start date).
      
      BUG: 345498
      BUG: 345565
      dc7b1865
    • Glen Ditchfield's avatar
      Add more tests for Recurrence::getNextDayTime(QDateTime) · 14b12d99
      Glen Ditchfield authored
      Also, edits the comments on getNextDayTime()'s declaration to make it
      plain that the the start dates are used, as opposed to the due dates.
      14b12d99
  25. 06 Jun, 2020 1 commit
  26. 09 May, 2020 1 commit
  27. 02 May, 2020 1 commit
  28. 11 Apr, 2020 1 commit
  29. 04 Apr, 2020 1 commit
  30. 30 Mar, 2020 1 commit
  31. 12 Mar, 2020 1 commit
  32. 07 Mar, 2020 2 commits