Re: A bug in Gtk+?
- From: Olexiy Avramchenko <olexiy ctech cn ua>
- To: Zeeshan Ali <zeenix gmail com>
- Cc: Gtk Mailing List <gtk-app-devel-list gnome org>, Stefan Kost <ensonic hora-obscura de>
- Subject: Re: A bug in Gtk+?
- Date: Wed, 23 Feb 2005 10:12:07 +0200
Zeeshan Ali wrote:
On Tue, 22 Feb 2005 15:22:50 +0100, Stefan Kost <ensonic hora-obscura de> wrote:
Are you sure?
Yeah I am sure and thats why i suspect that it may be pointing to a
bug in gtk+. Why don't you try it youself? Shouldn't take > 15 mins.
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.
1. Create separate context (this looks like the best solution).
2. Use gdk_threads_leave() before your g_main_loop_run() call.
Are you really need to use smth like that in your code ?
] [Thread Prev