From 9234fcb6248c41d09e46d4e5b7747f78052b2b83 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marco=20Trevisan=20=28Trevi=C3=B1o=29?= Date: Sat, 31 Aug 2019 17:48:43 +0200 Subject: [PATCH] event-x11: Use CLUTTER prefix for X11 filter docs As per commit ad72fa46b clutter_x11_handle_event was renamed into meta_x11_handle_event but the return type didn't change. So, keep the doc-string to match the actual possible return values. https://gitlab.gnome.org/GNOME/mutter/merge_requests/764 --- src/backends/x11/meta-event-x11.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backends/x11/meta-event-x11.c b/src/backends/x11/meta-event-x11.c index 8b4f4fc81..19da2235b 100644 --- a/src/backends/x11/meta-event-x11.c +++ b/src/backends/x11/meta-event-x11.c @@ -82,12 +82,12 @@ meta_x11_handle_event (XEvent *xevent) gboolean allocated_event; /* The return values here are someone approximate; we return - * META_X11_FILTER_REMOVE if a clutter event is + * CLUTTER_X11_FILTER_REMOVE if a clutter event is * generated for the event. This mostly, but not entirely, * corresponds to whether other event processing should be * excluded. As long as the stage window is not shared with another * toolkit it should be safe, and never return - * %META_X11_FILTER_REMOVE when more processing is needed. + * %CLUTTER_X11_FILTER_REMOVE when more processing is needed. */ result = CLUTTER_X11_FILTER_CONTINUE;