1. 11 Nov, 2020 2 commits
    • Alexander Lohnau's avatar
      Add KRunner KDE Store integration · bccf7e7d
      Alexander Lohnau authored
      FEATURE: 422929
      FIXED-IN: 5.21
      bccf7e7d
    • Konrad Materka's avatar
      Fix Connections warnings · 31cef000
      Konrad Materka authored
      Qt 5.15 introduced new syntax for defining Connections. Fix warnings like this one:
      QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
      31cef000
  2. 10 Nov, 2020 2 commits
  3. 09 Nov, 2020 2 commits
  4. 08 Nov, 2020 1 commit
  5. 07 Nov, 2020 1 commit
  6. 06 Nov, 2020 4 commits
  7. 05 Nov, 2020 3 commits
  8. 04 Nov, 2020 2 commits
    • Cyril Rossi's avatar
      KCM Notifications use KCModuleData to highlight the module when settings has changed · 46a7f880
      Cyril Rossi authored
      The particularity is in the per application/service's settings, which are created and loaded dynamically from the model in the KCM, meaning they are not yet available when KCModuleData check for isDefault.
      
      Simple solution introduced here is to allow the KCModuleData derived class to load them from the plasmanotifyrc file since the non default settings are saved here.
      
      Also, show the default indicator in the Applications / Services list and hihglight the "Configure..." button
      46a7f880
    • Script Kiddy's avatar
      SVN_SILENT made messages (.desktop file) - always resolve ours · a57104e7
      Script Kiddy authored
      In case of conflict in i18n, keep the version of the branch "ours"
      To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
      a57104e7
  9. 03 Nov, 2020 5 commits
  10. 01 Nov, 2020 2 commits
  11. 31 Oct, 2020 1 commit
  12. 30 Oct, 2020 2 commits
  13. 29 Oct, 2020 1 commit
  14. 28 Oct, 2020 1 commit
  15. 27 Oct, 2020 1 commit
  16. 26 Oct, 2020 2 commits
  17. 25 Oct, 2020 1 commit
    • Alexander Potashev's avatar
      Fix bug: Some user profile fields won't apply unless they all have unique new values. · 5cdff962
      Alexander Potashev authored
      Fixes the following bug: Some user profile fields won't apply unless
      they all have unique new values.
      
      STEPS TO REPRODUCE
      1. Start the Users KCM ("kcmshell5 kcm_users")
      2. Select a user
      3. Change the full name (the top-most input field) to "foo", change the
         email address to "foo@example.com", click Apply.
      4. Restart the Users KCM and make sure the change applied.
      5. Change the full name to "bar@example.com", change the email address
         to "bar@example.com" as well, click Apply.
      
      OBSERVED RESULT: The full name remains "foo", the email address is
      changed to "bar@example.com".
      
      EXPECTED RESULT: Both fields should change to "bar@example.com".
      
      Root cause: When the std::map used in UserApplyJob::start() is
      initialized, the key-value {"bar@example.com", full name setter ptr} is
      being overwritten by key-value {"bar@example.com", email setter ptr}.
      
      BUG: 427348
      5cdff962
  18. 24 Oct, 2020 3 commits
  19. 23 Oct, 2020 4 commits