Re: [Bug #2110] bug in threading implementation using guile-1.6.1

Re: [Bug #2110] bug in threading implementation using guile-1.6.1

[Mikael Djurfeldt]

nobody@savannah.gnu.org writes:

> =================== BUG #2110: LATEST MODIFICATIONS ==================
> http://savannah.gnu.org/bugs/?func=detailbug&bug_id=2110&group_id=39
>
> Changes by: Stan Pinte <stan.pinte@wanadoo.be>
> 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
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile

Re: [Bug #2110] bug in threading implementation using guile-1.6.1

[Stan Pinte]

On Fri, 10 Jan 2003 15:13:35 +0100, Mikael Djurfeldt <djurfeldt@nada.kth.se> 
 wrote:

> nobody@savannah.gnu.org writes:
>
>> =================== BUG #2110: LATEST MODIFICATIONS ==================
>> http://savannah.gnu.org/bugs/?func=detailbug&bug_id=2110&group_id=39
>>
>> Changes by: Stan Pinte <stan.pinte@wanadoo.be>
>> 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...

that is exactly the same as I get. thanks for helping.

>
> Best regards,
> Mikael Djurfeldt
>
>



-- 
Stan Pinte


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile