1. 11 Aug, 2020 4 commits
  2. 10 Aug, 2020 12 commits
  3. 09 Aug, 2020 1 commit
  4. 08 Aug, 2020 2 commits
  5. 07 Aug, 2020 2 commits
    • Florian Müllner's avatar
      ci: Remove pot file test · 8993de76
      Florian Müllner authored
      A recent Docker image update broke the test, as xgettext now prints
      the following warning:
      
      warning: a fallback ITS rule file '/usr/share/gettext-0.21/its/metainfo.its'
      is used; it may not be in sync with the upstream
      
      That is completely unrelated to what the test is meant to catch and
      could be fixed by adding appstream to the image, but considering that
      
       - the test didn't actually catch the last template string regression
       - we no longer allow template strings in files that include translatable
         strings (and enforce that with a CI job)
       - as of gettext 0.20.2, the template handling really really is fixed
         (we'll see)
      
      let's remove the test rather than piling up more stuff in the container
      image.
      
      !1399
      8993de76
    • emintufan's avatar
      Update Turkish translation · 01fedeed
      emintufan authored
      01fedeed
  6. 06 Aug, 2020 4 commits
  7. 04 Aug, 2020 2 commits
  8. 03 Aug, 2020 4 commits
    • verdre's avatar
      st/private: Multiply position in fb coordinates with resource scale · 18155fc6
      verdre authored
      The framebuffer we use for rendering shadows is scaled by the resource
      scale, that means we also need to offset coordinates when translating
      them to the framebuffers coordinate system.
      
      So far we forgot to do that when translating the framebuffer using the
      position of the actor, which lead to small rendering bugs of
      text-shadows for actors allocated at non-zero origins. To fix that,
      simply multiply those positions with the actors resource scale.
      
      !1390
      18155fc6
    • verdre's avatar
      appDisplay: Return false in acceptDrop when not accepting the drop · b83c93ad
      verdre authored
      Fix what is probably a copy-paste error and return false instead of a
      CONTINUE DragMotionResult which is only meant for dragMotion events, not
      drop events. This makes sure we don't create a folder when dropping an
      app over the drag leeways of another icon.
      
      !1389
      b83c93ad
    • Florian Müllner's avatar
      d0dab5a6
    • Florian Müllner's avatar
      status/network: Use D-Bus to launch Settings panels · c9708b14
      Florian Müllner authored
      For more obscure network configurations, we need to launch the
      corresponding Settings panel with additional parameters, so we
      cannot simply launch the .desktop file.
      
      However we can do better than spawning a command line: Control center
      exposes an application action we can use instead, so the process is
      launched with the appropriate activation environment and startup
      notification support.
      
      !1385
      c9708b14
  9. 02 Aug, 2020 1 commit
    • Andre Magalhaes's avatar
      rfkill: Always sync state on construction · dd846f1b
      Andre Magalhaes authored
      This fixes an issue where the indicator can be out of sync until the
      RfkillManager (used by it) properties change.
      
      The problem is that multiple instances of the indicator will use
      the same RfkillManager instance (getRfkillManager() returns a singleton)
      that only guarantees to emit the changed signal in two scenarios:
      when the D-Bus proxy connects and when the proxy properties change.
      
      If by the time an indicator is instantiated the RfkillManager's D-Bus
      proxy is already connected, that indicator would only sync its state
      when the RfkillManager properties change.
      
      Let's fix that by always syncing the state on construction - in the worst
      case scenario the RfkillManager's D-Bus proxy won't have connected yet
      and the indicator state will be temporarily out of sync but once it gets
      connected the indicator will sync again with the correct state.
      
      !1386
      dd846f1b
  10. 01 Aug, 2020 1 commit
  11. 31 Jul, 2020 7 commits