[mutter/wip/nielsdg/cursor-moved-marshal: 13/14] cursor-tracker: Don't use g_cclosure_marshal_VOID__VOID

[Carlos Garnacho <carlosg src gnome org>]

commit 4de892b02a38a1858c471482734eec61ecdb5c0d
Author: Niels De Graef <nielsdegraef gmail com>
Date:   Wed Jul 24 11:23:08 2019 +0200

    cursor-tracker: Don't use g_cclosure_marshal_VOID__VOID
    
    Similar to gtk commit f507a790, this ensures that the valist variant of
    the marshaller is used. From that commit's message:
    
    ```
    If we set c_marshaller manually, then g_signal_newv() will not setup a
    va_marshaller for us. However, if we provide c_marshaller as NULL, it will
    setup both the c_marshaller (to g_cclosure_marshal_VOID__VOID) and
    va_marshaller (to g_cclosure_marshal_VOID__VOIDv) for us.
    ```
    
    https://gitlab.gnome.org/GNOME/mutter/merge_requests/697

 src/backends/meta-cursor-tracker.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
---
diff --git a/src/backends/meta-cursor-tracker.c b/src/backends/meta-cursor-tracker.c
index 04f20cf15..4cbe0ec45 100644
--- a/src/backends/meta-cursor-tracker.c
+++ b/src/backends/meta-cursor-tracker.c
@@ -183,8 +183,7 @@ meta_cursor_tracker_class_init (MetaCursorTrackerClass *klass)
   signals[VISIBILITY_CHANGED] = g_signal_new ("visibility-changed",
                                               G_TYPE_FROM_CLASS (klass),
                                               G_SIGNAL_RUN_LAST,
-                                              0, NULL, NULL,
-                                              g_cclosure_marshal_VOID__VOID,
+                                              0, NULL, NULL, NULL,
                                               G_TYPE_NONE, 0);
 }