Hello,
On Wed, 23 Feb 2005 10:12:07 +0200, Olexiy Avramchenko
<[EMAIL PROTECTED]> wrote:
> When you create main loop with NULL as context parameter, main loop gets
> shared default context. Before you create your main loop, default
> context was populated with functions from gtk/gdk.
>
> The blocker is gdk_event_prepare (it just locks the global mutex), GLib
> code call it because the event source is not removed by gtk_main_quit.
Thanks. Got it :)
> You may:
> 1. Create separate context (this looks like the best solution).
> 2. Use gdk_threads_leave() before your g_main_loop_run() call.
I'll go for #1 i think.
> Are you really need to use smth like that in your code ?
Yep, in a software of mine that is for ATM machines. You mean to
ask why i am using both the GMainLoop and gtk_main* in the same
software, right? At one hand i dont want to bring in gtk+ (glib only)
into the card-reader interfacing module and OTOH i need nested main
loops inside the gui module, for which IMHO i'll need to do some more
labour if done using GMainLoop way. You may call it a "nessecity of my
laziness" :)
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
