[Glade-devel] I'd like to know an architectural decision

[tristan.van.berkom at gmail.com (Tristan Van Berkom)]

Ok after looking at the code again I see the possibility of recursion,
dont see what would make it hang
though, the idle handler should just queue another idle handler until
the widget is actually realized.

Rather, what should be done here is instead of using an idle,
g_signal_connect_after() to the "realize"
signal of the layout that we are waiting to be realized.

At any rate, if this is a bug for you then please, please file it in bugzilla.

Thankyou,
                   -Tristan

On Sun, May 4, 2008 at 6:08 PM, Pavel Kostyuchenko <shprotx at gmail.com> wrote:
> The problem is that it conflicts in fact. After anjuta has added its
>  idle handler, glade adds it's own handler, which appears to be called
>  earlier than anjuta's handler, then (because main window isn't
>  realized still) adds itself as idle handler and appears to be called
>  earlier again. In that way it adds itself to the idle handlers
>  infinitely.
>
>  On Sun, May 4, 2008 at 11:56 PM, Tristan Van Berkom
>
> <tristan.van.berkom at gmail.com> wrote:
>
> >  The g_idle_add() does not conflict with anything, its a timeout for
>  >  the first idle moment
>  >  and as such is more stable then adding any timeouts.
>  --
>  Regards,
>  Pavel