1. 26 Oct, 2017 1 commit
  2. 03 Oct, 2017 1 commit
  3. 02 Aug, 2017 1 commit
  4. 20 Jul, 2017 2 commits
  5. 08 Nov, 2016 1 commit
    • Florian Müllner's avatar
      gdkdisplay-wayland: Add API to set startup notification ID · 75ee402c
      Florian Müllner authored
      For wayland clients, the startup notification ID is currently only set
      from the DESKTOP_STARTUP_ID environment variable. As that variable is
      only set for clients launched via exec(), startup completion is not
      indicated correctly for DBus-activated applications unless an explicit
      ID is specified - usually that is not the case, as the default handling
      uses gdk_notify_startup_complete().
      To address this, we need API to set the startup notification ID from GTK
      as we have on X11.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=768531
      75ee402c
  6. 08 Sep, 2016 1 commit
  7. 29 Aug, 2016 2 commits
  8. 25 Aug, 2016 2 commits
  9. 22 Jul, 2016 1 commit
  10. 16 Jun, 2016 2 commits
  11. 18 May, 2016 1 commit
  12. 01 May, 2016 1 commit
  13. 28 Apr, 2016 1 commit
  14. 26 Apr, 2016 1 commit
    • Jonas Ådahl's avatar
      wayland: Clean up naming of GdkWaylandDisplay pointers · cb73becf
      Jonas Ådahl authored
      The naming of pointers to GdkWaylandDisplay's were inconsistent.
      Running the following commands in gtk+/gdk/wayland illustrate the
      inconsistency:
      
      $ grep -r '\<display_wayland\>' *.[ch] | wc -l
      195
      $ grep -r '\<wayland_display\>' *.[ch] | wc -l
      81
      
      This patch renames all occurrences of "wayland_display" to
      "display_wayland". This is also consistent with naming in the X11
      backend. A couple of whitespace changes were done as well in places
      where the rename was already done, that added line breaks to long lines
      that stood out.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=765474
      cb73becf
  15. 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
  16. 26 Mar, 2016 1 commit
  17. 10 Mar, 2016 2 commits
  18. 29 Feb, 2016 2 commits
  19. 28 Feb, 2016 1 commit
  20. 26 Feb, 2016 2 commits
  21. 19 Feb, 2016 1 commit
  22. 18 Feb, 2016 1 commit
  23. 06 Feb, 2016 3 commits
  24. 25 Jan, 2016 2 commits
  25. 22 Jan, 2016 1 commit
  26. 20 Jan, 2016 3 commits
  27. 19 Jan, 2016 1 commit
  28. 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