1. 10 Jul, 2021 1 commit
  2. 28 Jun, 2021 1 commit
  3. 16 Jun, 2021 2 commits
  4. 15 Jun, 2021 1 commit
  5. 09 May, 2021 1 commit
  6. 07 Apr, 2021 1 commit
  7. 20 Mar, 2021 1 commit
  8. 18 Mar, 2021 1 commit
  9. 17 Mar, 2021 1 commit
  10. 13 Mar, 2021 1 commit
  11. 08 Nov, 2020 1 commit
  12. 31 Oct, 2020 1 commit
  13. 15 Oct, 2020 1 commit
    • Nicolas Fella's avatar
      Follow release service version numbers · 0c9bfadb
      Nicolas Fella authored
      Ever since joining the release service we never increased our version number on release.
      I've seen distros automatically apply the release service version scheme (20.0X) to the package,
      but when running e.g. kdeconnect-cli -v we'd still get 1.4.
      
      This way the version is automatically adjusted by the release tooling so we don't need to care about and cannot forget it any longer.
      0c9bfadb
  14. 30 Jul, 2020 1 commit
    • Nicolas Fella's avatar
      Replace manual include dir handling with interface target · 79164ca8
      Nicolas Fella authored
      We use kdeconnect-version.h in several places and therefore it needs to be in the include path. We currently do this by setting target_include_path in a few places. Replace this with an interface library that we can link against that sets up the correct include path. IMO it is cleaner this way.
      79164ca8
  15. 05 Jul, 2020 1 commit
  16. 26 May, 2020 1 commit
    • Antonio Larrosa Jimenez's avatar
      Use ecm_qt_declare_logging_category to declare the logging categories · 1d361642
      Antonio Larrosa Jimenez authored
      This automatizes the generation of logging categories so a
      kdeconnect-kde.categories is generated and installed to
      /usr/share/qlogging-categories5/ so kdebugsettings can use it.
      
      Also, sets the default logging level to Warning. So now the logs
      of users won't be filled with debug messages but they can
      modify the configuration easily with kdebugsettings.
      1d361642
  17. 17 May, 2020 1 commit
  18. 22 Apr, 2020 1 commit
  19. 16 Apr, 2020 2 commits
  20. 13 Apr, 2020 1 commit
    • Philip Cohn-Cort's avatar
      Finally, we have support for sending out Battery information. · c315170b
      Philip Cohn-Cort authored
      ## Summary
      
      The core idea is as follows:
      
      1. When a Link loads the BatteryPlugin, we query Solid for a list of batteries.
          1. If the list is empty, we print a warning message and return quickly
          2. Otherwise, we connect *two signals* to every object in that list
      2. We send out a single new NetworkPacket as soon as we've processed that list
      3. When either of those two signals emits, we send another new NetworkPacket
      
      ### Multi-battery Support
      
      BUG: 357193
      
      To handle devices with multiple batteries (requested in that bug), we average
      together the battery percentages. This also includes a new field in the packet for
      'number of batteries' called `batteryQuantity`. For backwards compatibility, we can
      assume it has a default value of one.
      
      This should ensure we support
      - devices with no batteries at all (like many desktop machines)
      - devices with hot-pluggable batteries (like those laptops with detachable screens)
      
      ### Concerns
      
      Note that the implementation isn't perfect.
      We'll need some new localizable text to make it clear that we now support sending
      battery status information.
      
      Then there's a rather significant question: maybe we should have two battery plugins
      on each client, like we do for the `findmyphone`/`findthisdevice` plugins?
      
      ## Test Plan
      
      We need to ensure that other clients (including those using the Android codebase)
      will respond correctly. The main things to look at are
      1. are these new packets sent when the plugin is enabled, and not sent when it's disabled?
      2. is the charge percentage accurate?
      3. is the charge state (charging, discharging, or full) accurate?
      and
      4. do we see the correct number of warnings for low-battery?
      c315170b
  21. 17 Mar, 2020 1 commit
  22. 01 Mar, 2020 1 commit
  23. 17 Jan, 2020 1 commit
  24. 16 Jan, 2020 1 commit
  25. 06 Jan, 2020 1 commit
  26. 03 Jan, 2020 2 commits
  27. 09 Dec, 2019 1 commit
  28. 07 Dec, 2019 3 commits
  29. 27 Oct, 2019 7 commits