Attachment 50202 Details for Bug 37145 – IdleServerConnection: Replace g_signal_emit_by_name with g_signal_emit

[patch] IdleServerConnection: Replace g_signal_emit_by_name with g_signal_emit

0003-IdleServerConnection-Replace-g_signal_emit_by_name-w.patch (text/plain), 1.21 KB, created by Debarshi Ray on 2011-08-14 07:38:07 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Debarshi Ray

Created: 2011-08-14 07:38:07 UTC

Size: 1.21 KB

patch

obsolete

>From 5dbe5271f20c69c735632717c64f292aedea87a7 Mon Sep 17 00:00:00 2001
>From: Debarshi Ray <rishi@gnu.org>
>Date: Wed, 10 Aug 2011 15:34:03 +0200
>Subject: [PATCH 3/4] IdleServerConnection: Replace g_signal_emit_by_name with
> g_signal_emit
>
>---
> src/idle-server-connection.c |    4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/src/idle-server-connection.c b/src/idle-server-connection.c
>index 5f8b981..de46441 100644
>--- a/src/idle-server-connection.c
>+++ b/src/idle-server-connection.c
>@@ -230,7 +230,7 @@ static void change_state(IdleServerConnection *conn, IdleServerConnectionState s
> 	IDLE_DEBUG("emitting status-changed, state %u, reason %u", state, reason);
> 
> 	priv->state = state;
>-	g_signal_emit_by_name(conn, "status-changed", state, reason);
>+	g_signal_emit(conn, signals[STATUS_CHANGED], 0, state, reason);
> }
> 
> static void io_err_cleanup_func(gpointer data) {
>@@ -256,7 +256,7 @@ static void _input_stream_read_ready(GObject *source_object, GAsyncResult *res,
> 		goto disconnect;
> 	}
> 
>-	g_signal_emit_by_name(conn, "received", priv->input_buffer);
>+	g_signal_emit(conn, signals[RECEIVED], 0, priv->input_buffer);
> 
> 	if (g_cancellable_is_cancelled(priv->cancellable))
> 		goto disconnect;
>-- 
>1.7.6
>

Actions: View | Splinter Review

Attachments on bug 37145: 46707 | 46708 | 50200 | 50201 | 50202 | 50203 | 51938 | 51939 | 51940 | 51941 | 51942 | 51943 | 51944 | 51945 | 51946 | 51947 | 51948 | 51949 | 51950 | 51951 | 51952 | 51953 | 51954 | 51955

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.