[mutter/wip/wayland-work: 2/11] display: don't report extended barrier support on wayland



commit bd6536dec38c0a1c362f67f1641b1d9eadd5d1cc
Author: Giovanni Campagna <gcampagn redhat com>
Date:   Thu Aug 29 14:04:10 2013 +0200

    display: don't report extended barrier support on wayland
    
    Even if the xserver does them, they're useless because it doesn't
    get the pointer events.
    This is a lame workaround for not having real barriers in wayland,
    but it fixes the hot corner and message tray (because it triggers
    the old xserver path)

 src/core/display.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/src/core/display.c b/src/core/display.c
index 7d67c2e..7b8a217 100644
--- a/src/core/display.c
+++ b/src/core/display.c
@@ -5984,7 +5984,7 @@ meta_display_get_xinput_opcode (MetaDisplay *display)
 gboolean
 meta_display_supports_extended_barriers (MetaDisplay *display)
 {
-  return META_DISPLAY_HAS_XINPUT_23 (display);
+  return META_DISPLAY_HAS_XINPUT_23 (display) && !meta_is_wayland_compositor ();
 }
 
 /**


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]