Thanks Simon,
You are correct, it's actually ALL the D-Bus level arguments are on the
single JS argument as an array. My fault for assuming the interface would
be similar to the deprecated version.
What threw me was the second argument ':1.51'.
I'm curious what the second argument actually is (although I don't really
need it for my purposes)
Thanks again,
Louis.
On 1 May 2013 03:32, Simon McVittie <simon.mcvit...@collabora.co.uk> wrote:
> On 30/04/13 14:14, Louis des Landes wrote:
> > JS LOG: 5890,psyk...@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, 'psyk...@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
> _______________________________________________
> gnome-shell-list mailing list
> gnome-shell-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-shell-list
>
_______________________________________________
gnome-shell-list mailing list
gnome-shell-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-shell-list
