From 5b98cc7a3a2329a7ecaa4d9141eadd1ae73e0c9c Mon Sep 17 00:00:00 2001 From: Niels De Graef Date: Wed, 24 Jul 2019 11:34:35 +0200 Subject: [PATCH] cursor-tracker: Document cursor-moved signal It's a bit easier to track what's going on in a signal if you document it (otherwise you have to check where it was emitted in the code). https://gitlab.gnome.org/GNOME/mutter/merge_requests/697 --- src/backends/meta-cursor-tracker.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/backends/meta-cursor-tracker.c b/src/backends/meta-cursor-tracker.c index 4cbe0ec45..45291e286 100644 --- a/src/backends/meta-cursor-tracker.c +++ b/src/backends/meta-cursor-tracker.c @@ -167,6 +167,14 @@ meta_cursor_tracker_class_init (MetaCursorTrackerClass *klass) NULL, NULL, NULL, G_TYPE_NONE, 0); + /** + * MetaCursorTracker::cursor-moved: + * @cursor: The #MetaCursorTracker + * @x: The new X coordinate of the cursor + * @y: The new Y coordinate of the cursor + * + * Notifies when the cursor has moved to a new location. + */ signals[CURSOR_MOVED] = g_signal_new ("cursor-moved", G_TYPE_FROM_CLASS (klass), G_SIGNAL_RUN_LAST,