1. 09 May, 2017 1 commit
  2. 05 May, 2017 1 commit
  3. 02 May, 2017 1 commit
  4. 30 Apr, 2017 2 commits
  5. 28 Apr, 2017 1 commit
  6. 13 Apr, 2017 1 commit
  7. 07 Apr, 2017 3 commits
  8. 27 Mar, 2017 2 commits
  9. 24 Mar, 2017 1 commit
  10. 13 Mar, 2017 1 commit
  11. 09 Mar, 2017 1 commit
  12. 06 Mar, 2017 1 commit
  13. 17 Feb, 2017 1 commit
  14. 14 Feb, 2017 1 commit
    • Jonas Ådahl's avatar
      Make libmutter and friends parallel installable · 4ebc55f2
      Jonas Ådahl authored
      In order to minimize the amount of breakage, while at the same time
      making it easier to make backward incompatible changes needed to
      continue turning libmutter into a capable Wayland compositor, make the
      libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel
      installable by adding a version number to the name. This changes
      various filenames, for example what previously was libmutter.so is now
      libmutter-0.so (assuming the version for now is 0), and
      libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config
      filenames and GObject introspection has been renamed to reflect this as
      This enables a downstream compositor rely on a specific version of the
      libmutter API, while gracefully handling API/ABI changes by having to
      update to the new version at their own pace.
  15. 10 Feb, 2017 5 commits
  16. 02 Feb, 2017 1 commit
  17. 25 Jan, 2017 2 commits
    • Rui Matos's avatar
      clutter/evdev: Dispatch libinput before generating key repeat events · 1597b357
      Rui Matos authored
      Since both the libinput event source and the key repeat timer have the
      same priority, the order in which both handlers are called is
      arbitrary if both sources are ready on the same poll return. This
      means that sometimes we generate key repeats when there's already a
      real key event queued on libinput that would cancel the repeat timer
      if only it was processed before.
      One solution would be lowering the repeat timer source priority a
      notch lower than the libinput source but that would mean that a steady
      stream of events from libinput (e.g. pointer device motion) would
      prevent any key repeats to happen.
      Instead, we can fix this problem by trying to dispatch libinput from
      the key repeat timer and checking if the timer source has been
      destroyed before generating more key repeats.
    • Rui Matos's avatar
      clutter/evdev: Avoid losing key repeat timestamp resolution · 73524cad
      Rui Matos authored
      Commit 9214d502 changed the notify*
      API to use microseconds and we already have a microsecond time source
      here so we can use the timestamp directly without losing resolution at
      this layer.
  18. 23 Nov, 2016 3 commits
  19. 07 Nov, 2016 1 commit
  20. 04 Nov, 2016 9 commits
  21. 17 Oct, 2016 1 commit