On Mon, May 24, 2010 at 09:06, Tomeu Vizoso
wrote:
> On Sun, May 23, 2010 at 18:00, muppet wrote:
>>
>> On May 23, 2010, at 11:41 AM, Tomeu Vizoso wrote:
>>
>>> This implies that GDestroyNotify is per callback, but in this case we
>>> have two callbacks and a single GDestroyNotify.
>>>
>>> What a
On Sun, May 23, 2010 at 18:00, muppet wrote:
>
> On May 23, 2010, at 11:41 AM, Tomeu Vizoso wrote:
>
>> This implies that GDestroyNotify is per callback, but in this case we
>> have two callbacks and a single GDestroyNotify.
>>
>> What are bindings supposed to do in this case?
>
> Provided that bo
On May 23, 2010, at 11:41 AM, Tomeu Vizoso wrote:
> This implies that GDestroyNotify is per callback, but in this case we
> have two callbacks and a single GDestroyNotify.
>
> What are bindings supposed to do in this case?
Provided that both callbacks are invalidated when the object is destroye
Hi,
was giving a try at using GDBus from PyGI and found a showstopper right away.
g_bus_watch_proxy gets passed two callbacks and has a single user_data
and GDestroyNotify for both.
guint g_bus_watch_proxy (GBusType bus_type,