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
This commit is contained in:
parent
4de892b02a
commit
5b98cc7a3a
@ -167,6 +167,14 @@ meta_cursor_tracker_class_init (MetaCursorTrackerClass *klass)
|
|||||||
NULL, NULL, NULL,
|
NULL, NULL, NULL,
|
||||||
G_TYPE_NONE, 0);
|
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",
|
signals[CURSOR_MOVED] = g_signal_new ("cursor-moved",
|
||||||
G_TYPE_FROM_CLASS (klass),
|
G_TYPE_FROM_CLASS (klass),
|
||||||
G_SIGNAL_RUN_LAST,
|
G_SIGNAL_RUN_LAST,
|
||||||
|
Loading…
x
Reference in New Issue
Block a user