1. 02 Jul, 2022 1 commit
  2. 01 Jul, 2022 1 commit
  3. 21 Jun, 2022 1 commit
  4. 13 Jun, 2022 1 commit
  5. 12 Jun, 2022 1 commit
  6. 05 Jun, 2022 1 commit
    • Ahmad Samir's avatar
      Fix some "unknown property type" message when parsing a kservicetype · 9cb74ece
      Ahmad Samir authored and Alexander Lohnau's avatar Alexander Lohnau committed
      E.g. when building KIO:
      About to parse service type file "/usr/share/kservicetypes5/kcmodule.desktop"
      ....
      ...
      Found property definition "X-DocPath" with type "QString"
      Unknown property type for key "X-KDE-ParentApp" -> falling back to string
      Unknown property type for key "X-KDE-Keywords" -> falling back to string
      
      GIT_SILENT
      9cb74ece
  7. 04 Jun, 2022 1 commit
  8. 01 Jun, 2022 1 commit
  9. 31 May, 2022 1 commit
  10. 25 May, 2022 3 commits
  11. 23 May, 2022 1 commit
    • Alexander Lohnau's avatar
      Add debug output to print KCM location · 9a4d86af
      Alexander Lohnau authored
      This way one can better debug, from where the KCM was loaded. For example
      if one wants to know which KCMs were loaded from the kdesrc-build setup
      and which KCMs were loaded from the system setup.
      9a4d86af
  12. 15 May, 2022 2 commits
  13. 14 May, 2022 1 commit
  14. 13 May, 2022 1 commit
  15. 11 May, 2022 1 commit
  16. 04 May, 2022 1 commit
  17. 03 May, 2022 1 commit
  18. 02 May, 2022 1 commit
    • Alexander Lohnau's avatar
      KPluginModel: Add method to get KPluginMetaData config object for given plugin id · 888e28cb
      Alexander Lohnau authored
      Unlike KPluginSelector/KPluginWidget, the KPluginModel does not have the functionality to
      display the config of a plugin. Meaning consumers will need to take care of implementing a `showConfiguration` like method.
      For doing this we need the KPluginMetaData object of the config.
      
      For example the KRunner KCM has the functionality to open a plugin's config by passing in the
      plugin id to the args when creating the KCModule.
      888e28cb
  19. 28 Apr, 2022 1 commit
  20. 23 Apr, 2022 4 commits
  21. 18 Apr, 2022 2 commits
  22. 14 Apr, 2022 5 commits
  23. 09 Apr, 2022 1 commit
  24. 05 Apr, 2022 1 commit
  25. 02 Apr, 2022 1 commit
  26. 28 Mar, 2022 1 commit
  27. 23 Mar, 2022 1 commit
  28. 20 Mar, 2022 1 commit
  29. 14 Mar, 2022 1 commit
    • Alexander Lohnau's avatar
      Fix KPluginSelector KCMs missing their metadata on plugin loading · c9c58de6
      Alexander Lohnau authored
      For the KWin KCMs we need the full metadata, because we read the
      plugin keyword.
      
      Without the X-KDE-ConfigModule key, plugins used to create a symlink
      in the kservices5 folder to their metadata, which then goes through the
      legacy code path we would read all the metadata.
      This includes the plugin keyword.
      
      When consumers would this key, but have an old KWin version which
      used the KPluginSelector class and a kcmutils version which reads X-KDE-ConfigModule, but does not
      include this bugfix, the plugin keyword will be empty and thus the config
      files can not be located.
      
      This makes it hard to fix the loading on kcmutils < 5.91, but keeping the
      code working with KWin < 5.24.
      
      To test this, you should check out KWin 5.23 and kcmutils master.
      Fox example https://github.com/nclarius/tile-gaps/ will then fail
      to load it's config. With this change included, it should load properly.
      
      BUG: 444378
      c9c58de6