Re: Xlib unexpected async



>> >gdk_threads_enter();
>> >gtk_main();
>> >gdk_threads_leave();
>> 
>> why are you calling the thread functions at this level? they guarantee
>> that no other thread will ever be able to enter GTK, since the mutex
>> they operate on will be held for the entire duration of the GUI's
>> existence. 
>
>GTK+ releases the lock during gtk_main(). In fact, the
>gdk_threads_enter/leave pair here is required.

gtk_signal_connect(GTK_OBJECT(me), "foot", &mouth, NULL);

--p (who uses threads always but never uses gdk_threads_{enter,leave})




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]