Members of the KDE Community are recommended to subscribe to the kde-community mailing list at https://mail.kde.org/mailman/listinfo/kde-community to allow them to participate in important discussions and receive other important announcements

  1. 08 Aug, 2020 1 commit
  2. 04 Aug, 2020 1 commit
    • Alexander Lohnau's avatar
      Save RunnerContext after each match session · 45d42bb9
      Alexander Lohnau authored
      CCBUG: 424505
      If we only save the context in the deconstructor the
      entries don't get saved when we kill krunner/shutdown/reboot.
      Currently they only get saved when we end krunner using
      `kquitapp5 krunner`.
      
      The history items are also synced after each session.
      45d42bb9
  3. 03 Aug, 2020 1 commit
    • Alexander Lohnau's avatar
      Remove dead debug code · 45efefd8
      Alexander Lohnau authored
      This code has been commented out since forever and is only irritating.
      But the total numbers of runners is IMO a useful debug information
      45efefd8
  4. 01 Aug, 2020 1 commit
  5. 30 Jul, 2020 1 commit
  6. 25 Jul, 2020 1 commit
  7. 24 Jul, 2020 1 commit
  8. 23 Jul, 2020 1 commit
  9. 22 Jul, 2020 2 commits
  10. 14 Jul, 2020 2 commits
    • Friedrich W. H. Kossebau's avatar
      Allow removing deprecated virtual method from own build · 64badabf
      Friedrich W. H. Kossebau authored
      Virtual methods and other things with ABI-sideeffects beyond own symbol
      can be wrapped with the *_BUILD_DEPRECATED_SINCE(x,y) in the headers,
      to enable builds without those. These macros are only influenced by
      variables baked into the build of the library (i.e. the export header),
      cannot be controlled from 3rd-party, so results in a stable ABI.
      
      CCBUG: 423003
      GIT_SILENT
      64badabf
    • David Redondo's avatar
      Do not remove virtual method from build · 8f7ce559
      David Redondo authored
      Method was deprecated in fc5738ab. Removing the
      method when building without deprecated methods (for example the pim runner
      does this) changes the vtable leading to crashes.
      BUG: 423003
      8f7ce559
  11. 13 Jul, 2020 3 commits
  12. 12 Jul, 2020 1 commit
  13. 07 Jul, 2020 2 commits
  14. 05 Jul, 2020 1 commit
  15. 04 Jul, 2020 1 commit
  16. 19 Jun, 2020 2 commits
  17. 18 Jun, 2020 1 commit
  18. 17 Jun, 2020 1 commit
  19. 13 Jun, 2020 2 commits
  20. 08 Jun, 2020 2 commits
  21. 06 Jun, 2020 1 commit
  22. 05 Jun, 2020 1 commit
  23. 31 May, 2020 1 commit
  24. 28 May, 2020 1 commit
  25. 27 May, 2020 2 commits
    • Alexander Lohnau's avatar
      041f76ed
    • Alexander Lohnau's avatar
      KRunner fix prepare/teardown signals · 7c365354
      Alexander Lohnau authored
      Summary:
      BUG: 420311.
      Because the teardown was requested and checked the prepped variable was set to false and consequently
      the prepare method gets called for the next character typed.
      
      The exact two lines get called in the `matchSessionComplete` method.
      The `matchSessionComplete` method gets called called in `RunnerResultsModel::clear` (milou repo).
      
      Test Plan:
      If you connect to the prepare/teardown slot, for example:
      ```
      connect(this, &MyRunner::prepare, [=]() {
              qWarning() << "prepare";
      });````
      
      You see that they get triggered for each letter typed, after applying this patch they get only triggered when the match session is started/is over.
      
      Reviewers: meven, ngraham, broulik
      
      Reviewed By: meven
      
      Subscribers: davidedmundson, cfeck, kde-frameworks-devel
      
      Tags: #frameworks, #plasma
      
      Differential Revision: https://phabricator.kde.org/D29050
      7c365354
  26. 26 May, 2020 1 commit
  27. 25 May, 2020 1 commit
  28. 23 May, 2020 2 commits
  29. 19 May, 2020 1 commit
  30. 11 May, 2020 1 commit