[Glade-devel] I'd like to know an architectural decision
Pavel Kostyuchenko
shprotx at gmail.com
Sun May 4 17:08:19 EDT 2008
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
More information about the Glade-devel
mailing list