1. 09 Sep, 2016 1 commit
    • Jonas Ådahl's avatar
      clutter: Compress instead of discard motion events · d893adb2
      Jonas Ådahl authored
      Clutter discards any motion event if next event happens to also be a
      motion event. This is problematic when the motion event carries
      relative motion deltas, since the information about them is completely
      lost.
      
      Until we have moved away made the stage stop discarding motion events,
      lets work around the issue by compressing them, effectively adding
      multiple relative motion deltas together, would one be discarded.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=771049
      d893adb2
  2. 10 Aug, 2016 6 commits
  3. 22 Jul, 2016 3 commits
  4. 20 Jul, 2016 1 commit
  5. 03 May, 2016 3 commits
  6. 12 Apr, 2016 1 commit
  7. 16 Feb, 2016 5 commits
  8. 14 Jan, 2016 1 commit
  9. 03 Dec, 2015 1 commit
  10. 18 Nov, 2015 3 commits
  11. 17 Nov, 2015 1 commit
  12. 23 Oct, 2015 1 commit
  13. 12 Oct, 2015 2 commits
  14. 24 Jul, 2015 1 commit
  15. 10 Jul, 2015 1 commit
  16. 18 Mar, 2015 1 commit
    • Jonas Ådahl's avatar
      evdev: Keep track of the pointer coordinate ourself · 615b0f46
      Jonas Ådahl authored
      When multiple relative motion events are received and queued, we can't
      base the relative => absolute motion conversion off of the stage pointer
      position, since that is only updated when the queue is processed at
      the beginning of each frame. The effect of trying to use the stage
      pointer position was that subsequent motion events were effectively
      dropped.
      
      To improve things, switch to keeping track of the pointer position
      ourselves in the evdev backend and adding to that.
      
      This has the side effect of making the internal function
      _clutter_input_device_set_coords not effect the internal coordinate
      state of the evdev stage, but AFAICS there is nothing depending on that
      so that should be fine.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=746328
      615b0f46
  17. 03 Mar, 2015 1 commit
  18. 04 Feb, 2015 2 commits
    • Jonas Ådahl's avatar
      evdev: Ignore non seat wide pointer button events · e9e9578d
      Jonas Ådahl authored
      Pointer button events will be received from a device where a button has
      been pressed, even though an equivalent button has been pressed (same
      button code) on a device connected to the same seat. notify_button()
      expects to only be called as if there was only one pointer device
      associated with the given seat, so to achieve this, ignore every event
      where forwarding it would result in multiple 'pressed' or 'released'
      notifications.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=743615
      e9e9578d
    • Jonas Ådahl's avatar
      evdev: Ignore non seat wide keyboard key events · 32ce45aa
      Jonas Ådahl authored
      Keyboard key events will be received from a device where a key has
      been pressed, even though an equivalent key has been pressed (same
      key code) on a device connected to the same seat. notify_key()
      expects to only be called as if there was only one keyboard device
      associated with the given seat, so to achieve this, ignore every event
      where forwarding it would result in multiple 'pressed' or 'released'
      notifications.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=743615
      32ce45aa
  19. 16 Jan, 2015 1 commit
  20. 03 Jan, 2015 1 commit
    • Emmanuele Bassi's avatar
      WARNING: Massive revert commit · 77ec8774
      Emmanuele Bassi authored
      Revert all the work that happened on the master branch.
      
      Sadly, this is the only way to merge the current development branch back
      into master.
      
      It is now abundantly clear that I merged the 1.99 branch far too soon,
      and that Clutter 2.0 won't happen any time soon, if at all.
      
      Since having the development happen on a separate branch throws a lot of
      people into confusion, let's undo the clutter-1.99 → master merge, and
      move back the development of Clutter to the master branch.
      
      In order to do so, we need to do some surgery to the Git repository.
      
      First, we do a massive revert in a single commit of all that happened
      since the switch to 1.99 and the API version bump done with the
      89a2862b commit. The history is too long
      to be reverted commit by commit without being extremely messy.
      77ec8774
  21. 14 Oct, 2014 1 commit
  22. 21 Aug, 2014 1 commit
  23. 07 Aug, 2014 1 commit