1. 26 Oct, 2017 1 commit
  2. 02 Aug, 2017 1 commit
  3. 20 Jul, 2017 1 commit
    • Jonas Ådahl's avatar
      wayland: Throttle system bell requests · 376ff1ae
      Jonas Ådahl authored
      If a bad behaving application tries to make the window/display beep too
      often, throttle the beep requests so that we don't end up filling the
      Wayland socket queue.
      
      The throttle is set to 50 beeps per second, which far more beeps than
      will ever make any sense from a user experience point of view, but will
      avoid terminating due to an excessive amount of requests.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=778188
      376ff1ae
  4. 09 Jan, 2017 1 commit
    • Carlos Garnacho's avatar
      wayland: Disable EGL swap interval · ab66c3d7
      Carlos Garnacho authored
      We have a frame clock that ensures rendering is done as per the
      output vsync. There is no need to have Mesa do the same for us.
      
      This, most notably, ensures Mesa doesn't schedule frame callbacks
      that will be left unattended if the compositor stops throttling
      frames for its surface, this is eg. the case if the toplevel is
      moved to another workspace.
      
      Also, given a SwapInterval!=0 will always bring these unexpected
      side effects, check that it's possible to disable it, and spew
      a debug message if that isn't the case.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=769835
      ab66c3d7
  5. 02 Sep, 2016 1 commit
  6. 29 Aug, 2016 2 commits
  7. 25 Aug, 2016 1 commit
  8. 22 Jul, 2016 2 commits
  9. 28 Apr, 2016 1 commit
  10. 26 Apr, 2016 1 commit
  11. 06 Apr, 2016 1 commit
    • Stephen Chandler Paul's avatar
      Wayland: Add initial support for drawing tablets · 7cc0850a
      Stephen Chandler Paul authored
      Only the management of tablets and tools is added so far. No tablet events
      are yet interpreted.
      
      As it's been the tradition in GTK+, erasers are split into their own device,
      whereas the rest of the tools are meant to be routed through the
      GDK_SOURCE_PEN device. Both pen/eraser devices are slaves to a master
      pointer device, separate to wl_pointer's. This is so each tablet can
      maintain its own cursor/positioning accounting.
      Signed-off-by: default avatarStephen Chandler Paul <thatslyude@gmail.com>
      7cc0850a
  12. 10 Mar, 2016 1 commit
    • Jonas Ådahl's avatar
      wayland: Don't invent our own unstable protocol semantics · f68cf698
      Jonas Ådahl authored
      The gtk_shell protocol used some half baked unstable protocol semantics
      that worked by only allowing binding the exact version of the
      interface. This hack is a bit too confusing and it makes it impossible
      to do any compatible changes without breaking things.
      
      So, instead rename it to include a number in the interface names. This
      way we can add requests and events without causing compatibility issues,
      and we can later remove requests and events by bumping the number in
      the interface names.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=763001
      f68cf698
  13. 29 Feb, 2016 1 commit
  14. 26 Feb, 2016 1 commit
  15. 19 Feb, 2016 1 commit
  16. 19 Jan, 2016 1 commit
  17. 18 Jan, 2016 1 commit
    • Peter Hutterer's avatar
      wayland: add support for wl_pointer frame/axis_source/axis_discrete/axis_stop · 3fca3616
      Peter Hutterer authored
      This adds support for the new wl_pointer events available in v5.
      
      The wl_pointer.axis_source events can be ignored for the purposes here, the
      main reason they exist is so that the combination of axis_source=finger and
      axis_stop triggers kinetic scrolling. We don't need to care about the source,
      axis_stop is enough for us to tell us when we're scrolling.
      
      The wl_pointer.frame events group events together and is intended as a
      mechanism to coalesce events together. This for example allows us to now
      send a single GTK scroll event for a diagonal scroll. Previously, the two
      wl_pointer.axis events had to be handled separately.
      
      The wl_pointer.axis_discrete event sends mouse wheel clicks where
      appropriate, and is translated into up/down/left/right scroll events.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=756729
      3fca3616
  18. 26 Nov, 2015 2 commits
  19. 21 Aug, 2015 1 commit
  20. 12 Aug, 2015 1 commit
    • Carlos Garnacho's avatar
      wayland: Implement touchpad gesture events · 45d15b30
      Carlos Garnacho authored
      On wayland, the gestures protocol defines a wl_pointer_gestures global
      object, that will match in number with wl_seats, swipe and pinch
      interfaces can be obtained from it, which events are translated into
      GdkEventTouchpadSwipe/Pinch events.
      45d15b30
  21. 20 May, 2015 2 commits
  22. 16 Mar, 2015 1 commit
  23. 28 Feb, 2015 1 commit
  24. 13 Oct, 2014 2 commits
  25. 01 Sep, 2014 1 commit
  26. 26 Aug, 2014 1 commit
  27. 10 Aug, 2014 1 commit
  28. 16 May, 2014 2 commits
  29. 18 Nov, 2013 1 commit
  30. 03 Sep, 2013 2 commits
  31. 16 Jul, 2013 1 commit
  32. 26 Mar, 2013 1 commit
  33. 22 Mar, 2013 1 commit