1. 02 Dec, 2015 1 commit
  2. 17 Nov, 2015 1 commit
  3. 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
  4. 15 Nov, 2015 1 commit
  5. 03 Nov, 2015 1 commit
  6. 27 Oct, 2015 1 commit
  7. 20 Oct, 2015 1 commit
  8. 17 Oct, 2015 1 commit
  9. 13 Oct, 2015 1 commit
  10. 07 Oct, 2015 2 commits
  11. 06 Oct, 2015 1 commit
  12. 21 Sep, 2015 1 commit
  13. 09 Sep, 2015 2 commits
  14. 01 Aug, 2015 1 commit
    • Matthias Clasen's avatar
      Code cleanup · 9f24b547
      Matthias Clasen authored
      Use g_slist_free_full more consistently. This commit just converts
      the obvious cases where g_slist_forall is directly followed by
      g_slist_free.
      9f24b547
  15. 28 Jul, 2015 1 commit
    • Matthias Clasen's avatar
      x11: Make selection handling work across screens · 55edc81c
      Matthias Clasen authored
      When dealing with selection events, we might see windows from
      other screens in the requestor field. The current x11 backend
      code fails to wrap these in a foreign GdkWindow, since we
      don't have the corresponding GdkScreen anymore. Work around
      this by creating such 'foreign screens' on demand. We still
      maintain the 1:1 relation between the display and the screen
      returned by gdk_display_get_default_screen().
      
      https://bugzilla.gnome.org/show_bug.cgi?id=721398
      55edc81c
  16. 17 Jul, 2015 1 commit
  17. 15 Jul, 2015 3 commits
    • Carlos Garnacho's avatar
      Revert "x11: Query pointer devices' scroll valuators on toplevel enter events" · 72bfb40c
      Carlos Garnacho authored
      This reverts commit 77b8495b.
      
      The commit broke more scenarios than fixed, better to go back to square one.
      72bfb40c
    • Owen W. Taylor's avatar
      GdkDisplayX11: Properly translate server timestamps from _NET_WM_FRAME_* messages · 6504b2e5
      Owen W. Taylor authored
      When using frame times from _NET_WM_FRAME_DRAWN and _NET_WM_FRAME_TIMINGS, we
      were treating them as local monotonic times, but they are actually extended-precision
      versions of the server time, and need to be translated to monotonic times in the
      case where the X server and client aren't running on the same system.
      
      This fixes rendering stalls when using X over a remote ssh connection.
      https://bugzilla.gnome.org/show_bug.cgi?id=741800
      6504b2e5
    • Ryan Lortie's avatar
      GtkApplication: avoid using stale timestamps · a00a5ed2
      Ryan Lortie authored
      Avoid using a stale timestamp (from the last user interaction with the
      application) when a message arrives from D-Bus requesting that a new
      window be created.
      
      In this case the most-correct thing that we can do is to use no
      timestamp at all.
      
      We modify gdk_x11_display_set_startup_notification_id() to allow a NULL
      value to mean "reset everything" and then call this function
      unconditionally on receipt of D-Bus activation requests.  The result
      will be that a missing desktop-startup-id in the platform-data struct
      will reset the timestamp.
      
      Under their default configuration metacity and mutter will both map
      windows presented with no timestamp in the foreground.  This could
      result in false-positive, but there is very little we can do about that
      without the original timestamp from the user event.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=752000
      a00a5ed2
  18. 08 Jul, 2015 1 commit
    • Matthias Clasen's avatar
      Simplify Xft setting fallback · bdf0820c
      Matthias Clasen authored
      If we don't find Xft values in the X resource db, simply fall
      back to the values that are hardcoded in /etc/X11/Xresources
      anyway. Extra trickery with likely-made-up screen dimensions
      is not going to yield better results, and only makes for a
      deeper rabbit hole when debugging.
      bdf0820c
  19. 06 Jul, 2015 1 commit
  20. 01 Jul, 2015 2 commits
  21. 14 Jun, 2015 1 commit
  22. 02 Jun, 2015 1 commit
  23. 22 May, 2015 3 commits
  24. 08 May, 2015 1 commit
  25. 02 May, 2015 1 commit
    • Matthias Clasen's avatar
      xi2: Don't set button mask 4 and 5 · 2feaf8f9
      Matthias Clasen authored
      We interpret buttons 4-7 as old-school scroll events, so it does
      not make sense to add these to the mask. Also fix an off-by-one
      in the loop here, buttons_mask is 1-based.
      2feaf8f9
  26. 27 Apr, 2015 1 commit
  27. 13 Apr, 2015 1 commit
  28. 05 Apr, 2015 1 commit
  29. 26 Mar, 2015 1 commit
  30. 25 Mar, 2015 2 commits
  31. 23 Mar, 2015 2 commits