[Glade-devel] I'd like to know an architectural decision
- From: shprotx at gmail.com (Pavel Kostyuchenko)
- Subject: [Glade-devel] I'd like to know an architectural decision
- Date: Mon, 5 May 2008 17:50:59 +0300
I had made a patch for all mentioned bugs before I wrote a message to
anjuta mailing list, but something new appears to be broken after that
patch, so I thought I should discuss all that bugs before submitting
the patch. The patch has g_idle_ad replaced with "realized" signal,
but for unknown reason I need to call {container_remove,
container_add, show_all} two times else graphical designer window
appears to be not usable.
On Mon, May 5, 2008 at 12:53 AM, Tristan Van Berkom
<tristan.van.berkom at gmail.com> wrote:
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.
--
Regards,
Pavel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]