[EMAIL PROTECTED] writes: > =================== BUG #2110: LATEST MODIFICATIONS ================== > http://savannah.gnu.org/bugs/?func=detailbug&bug_id=2110&group_id=39 > > Changes by: Stan Pinte <[EMAIL PROTECTED]> > Date: 2003-Jan-10 13:38 (GMT) > > ------------------ Additional Follow-up Comments ---------------------------- > This only seems to happen when I make two calls two (gtk-main), indirectly. > > -> one via the (gtk-ensure-handler) call > -> one afterwards, via the (gtk-main) call.
Well, this is not a correct usage pattern. (gtk-ensure-handler) spawns a gtk handler which handles all events of the application. That is, it is an *alternative* to (gtk-main). If your intention with calling gtk-main is to wait for the application to quit, I suggest that you wait on a condition variable instead. Then make sure that it is signalled when the application quits. (But maybe someone else more versed in guile-gtk have a better suggestion.) If I do what you describe in an interactive guile session, I get a lot of glib warning messages which are properly informative: g_main_iterate(): main loop already active in another thread It would of course be nicer not to get stuck in a loop but just get *one* error message... Best regards, Mikael Djurfeldt _______________________________________________ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
