1. 08 Dec, 2015 1 commit
  2. 04 Dec, 2015 1 commit
  3. 03 Dec, 2015 1 commit
  4. 02 Dec, 2015 2 commits
  5. 01 Dec, 2015 5 commits
  6. 30 Nov, 2015 1 commit
    • Carlos Garnacho's avatar
      wayland: Refactor selection ownership · 4f9d0c06
      Carlos Garnacho authored
      Dissociate ownership from our maintenance of wl_data_source objects.
      The only place where ownership must be updated together is
      data_source.cancelled, for the other places GDK should take care of
      setting up the right ownership, even if at a different order than
      we'd expect here.
      
      This fixes GTK+ apps on wayland being locally confused about the
      current selection ownership. Because gtk_selection_add_targets()
      results in a wl_data_source being created, and ownership being
      updated right away, early callers of this will change the ownership
      even if the widget it's being called on didn't explicitly request
      the selection ownership yet.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=758660
      4f9d0c06
  7. 26 Nov, 2015 5 commits
  8. 24 Nov, 2015 4 commits
  9. 22 Nov, 2015 2 commits
  10. 20 Nov, 2015 1 commit
  11. 19 Nov, 2015 8 commits
  12. 17 Nov, 2015 2 commits
  13. 16 Nov, 2015 1 commit
    • Matthias Clasen's avatar
      x11: Try harder to find a core pointer · c6592929
      Matthias Clasen authored
      We currently just look for a master device with input source MOUSE.
      After recent changes to the way input devices are classified, xwayland
      on my system comes up with a virtual core pointer that has input
      source TOUCHSCREEN. This was causing assertion failures. Be a little
      more careful and accept a touchscreen as core pointer, if there is
      no mouse.
      c6592929
  14. 15 Nov, 2015 2 commits
  15. 13 Nov, 2015 2 commits
  16. 12 Nov, 2015 2 commits