Re: g_bus_watch_proxy and introspection

2010-05-24 Thread Tomeu Vizoso
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

Re: g_bus_watch_proxy and introspection

2010-05-24 Thread Tomeu Vizoso
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

Re: g_bus_watch_proxy and introspection

2010-05-23 Thread muppet
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

g_bus_watch_proxy and introspection

2010-05-23 Thread Tomeu Vizoso
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,