1. 16 Jul, 2020 2 commits
  2. 13 Nov, 2019 1 commit
  3. 23 Aug, 2016 1 commit
    • Carlos Garnacho's avatar
      gdk: Add pad event structs, enum values, and event mask bit · 0dcb9b31
      Carlos Garnacho authored
      GDK_PAD_BUTTON*,RING and STRIP will be emitted respectively when
      pad buttons, rings or strips are interacted with. Each of those
      pad components belong to a group (a pad can contain several of
      those), which may be in a given mode. All this information is
      contained in the event.
      
      GDK_PAD_GROUP_MODE is emitted when a group in the pad switches
      mode, which will generally result in a different set of actions
      being triggered from the same buttons/rings/strips in the group.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=770026
      0dcb9b31
  4. 10 May, 2016 3 commits
  5. 01 May, 2016 3 commits
  6. 22 Apr, 2016 2 commits
  7. 06 Apr, 2016 1 commit
  8. 14 Mar, 2016 1 commit
    • Carlos Garnacho's avatar
      gdkdnd: Add private means to commit the drag status · 2923f69d
      Carlos Garnacho authored
      The way gdk_drag_status() may be called multiple times during the
      processing of drag and drop events throughout the widget hierarchy
      brings some superfluous messaging going in, esp. when it's the last
      request the one we want to honor, yet we emit messaging requests on
      all.
      
      This is barely appreciable in the X11 backend, but due to the design
      of the wayland protocol, quick series of changes like this it have
      some self-amplificating consequences which may end up flooding the
      connection.
      
      We can delegate this to a late "commit" call, performed within GDK
      event management. This way gdk_drag_status() calls may be cached
      and only result in windowing messaging once per ::drag-motion or
      ::drag-data-received event. Emitting the final status will also
      avoid spurious action changes on the compositor and the other peer.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=763298
      2923f69d
  9. 11 Mar, 2016 1 commit
  10. 02 Mar, 2016 1 commit
  11. 28 Feb, 2016 2 commits
  12. 24 Feb, 2016 1 commit
  13. 19 Jan, 2016 1 commit
  14. 18 Jan, 2016 1 commit
  15. 16 Dec, 2015 3 commits
  16. 15 Dec, 2015 1 commit
  17. 14 Dec, 2015 1 commit
  18. 20 Oct, 2015 1 commit
  19. 19 Aug, 2015 1 commit
    • Carlos Garnacho's avatar
      gdkevent: Hold refs to device/source_device · 25557c1c
      Carlos Garnacho authored
      The extra reference will be held from GdkEventPrivate data, so there's
      a common place to all events. Without this, events queued after devices/
      capabilities disappear (eg. on TTY switch) might hold invalid pointers.
      Windowing level operations on those devices (queries, grabs...) are
      expected to fail at that time, but we should hold meaningful data for
      the regular event handling paths.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=753185
      25557c1c
  20. 12 Aug, 2015 1 commit
  21. 24 Jul, 2015 2 commits
  22. 01 Nov, 2014 1 commit
  23. 28 Oct, 2014 1 commit
  24. 12 Jun, 2014 1 commit
    • Matthias Clasen's avatar
      Drop GDK_MULTIHEAD_SAFE · 5334fb89
      Matthias Clasen authored
      We don't support multiple screens anymore, so there is no need
      for marking API as multihead safe any longer.
      5334fb89
  25. 23 May, 2014 1 commit
  26. 19 May, 2014 1 commit
  27. 13 May, 2014 1 commit
    • Jasper St. Pierre's avatar
      gdk: Add new _gdk_set_window_state · c1efc4ad
      Jasper St. Pierre authored
      Wayland's mechanism tells us all of our new states, rather than
      telling us which ones were added and removed. Add a new private
      interface so that we can simply specify the new states as a
      bitfield directly rather than having to compute which ones were
      added and removed.
      c1efc4ad
  28. 11 May, 2014 1 commit
  29. 19 Feb, 2014 1 commit
  30. 15 Feb, 2014 1 commit