Re: Gio.DBusProxy munging Signal callback arguments
- From: Simon McVittie <simon mcvittie collabora co uk>
- To: gnome-shell-list gnome org
- Subject: Re: Gio.DBusProxy munging Signal callback arguments
- Date: Tue, 30 Apr 2013 18:32:27 +0100
On 30/04/13 14:14, Louis des Landes wrote:
JS LOG: 5890,psyker7 hotmail com,<FONT FACE="Segoe UI"><FONT
COLOR="#000000">Message Received Here</FONT></FONT>,14783,2
Is this maybe the printed form of a JavaScript list, so
makeProxyWrapper.connectSignal() actually results in this call?
_messageDisplayed(':1.51',
[5890, 'psyker7 hotmail com', '<FONT...', 14783, 2])
In other words: the D-Bus-level arguments turn into one JS-level argument?
makeProxyWrapper() is part of something JavaScript-specific, not part of
GIO itself, so it won't necessarily map 1:1 between Python and
JavaScript. The underlying GIO facility is the GDBusProxy::g-signal
signal, which encodes the D-Bus-level signal arguments in one C argument
(a GVariant tuple).
S
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]