[mutter/gnome-3-16] core/events: Invalidate monitor cache when we're a wayland compositor
- From: Rui Matos <rtcm src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [mutter/gnome-3-16] core/events: Invalidate monitor cache when we're a wayland compositor
- Date: Thu, 30 Apr 2015 12:02:29 +0000 (UTC)
commit 7f0ed14f02fbddea0e2532eec47a1062a915fde1
Author: Rui Matos <tiagomatos gmail com>
Date: Wed Apr 29 16:20:38 2015 +0200
core/events: Invalidate monitor cache when we're a wayland compositor
When running as an X11 compositor we do this for every event we see on
the X event stream. As a wayland compositor we don't go through that
code path but since we see all events we can easily do this on motion
events.
In fact, we don't even need this caching when we're a wayland
compositor since we can always find where the pointer is without a
round trip but we're sharing the current monitor logic with the X
path so let's keep it as is for now.
https://bugzilla.gnome.org/show_bug.cgi?id=748478
src/core/events.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
---
diff --git a/src/core/events.c b/src/core/events.c
index 263f76b..5cd88b5 100644
--- a/src/core/events.c
+++ b/src/core/events.c
@@ -201,6 +201,7 @@ meta_display_handle_event (MetaDisplay *display,
{
MetaCursorTracker *tracker = meta_cursor_tracker_get_for_screen (NULL);
meta_cursor_tracker_update_position (tracker, event->motion.x, event->motion.y);
+ display->monitor_cache_invalidated = TRUE;
}
handle_idletime_for_event (event);
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]