Alexander Larsson wrote:
On Tue, 2008-12-30 at 21:47 -0500, Yu Feng wrote:
Dear Devels:
I am having troubles because the GMutex used gdk_threads_enter/leave can
be non-recursive.
IMHO that is a Gtk+ bug. When loading the modules from GTK_MODULE it
should take the Gdk lock in order to
On Tue, 2008-12-30 at 21:47 -0500, Yu Feng wrote:
Dear Devels:
I am having troubles because the GMutex used gdk_threads_enter/leave can
be non-recursive.
I have a piece of code (g_module_check_init) to either be called from an
event dispatched by GDK(if the module is loaded via
Hi Friends,
Thanks for the hint.
I don't have the luxury to override the gdk locking functions since I am
writing a plugin module for arbitrary applications; the application may
also want to override the locking functions.
This is the solution I came up with:
in gtk_module_init, I defer the
On Sun, Jan 4, 2009 at 5:14 AM, Alexander Larsson al...@redhat.com wrote:
IMHO that is a Gtk+ bug.
I agree. Yu, can you file a bug about this ?
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
On Sun, 2009-01-04 at 15:43 -0500, Matthias Clasen wrote:
On Sun, Jan 4, 2009 at 5:14 AM, Alexander Larsson al...@redhat.com wrote:
IMHO that is a Gtk+ bug.
I agree. Yu, can you file a bug about this ?
Yes. Filed as Bug 566578
Yu
___
The code need to be protected so that its execution is not interrupted
by GDK activities in other threads. How can I do this without a
recursive gdk critical section?
Don't use GTK+ from multiple threads. Makes the code a lot cleaner.
--tml
___
On Wed, 2008-12-31 at 15:11 +0200, Tor Lillqvist wrote:
The code need to be protected so that its execution is not interrupted
by GDK activities in other threads. How can I do this without a
recursive gdk critical section?
Don't use GTK+ from multiple threads. Makes the code a lot
Dear Devels:
I am having troubles because the GMutex used gdk_threads_enter/leave can
be non-recursive.
I have a piece of code (g_module_check_init) to either be called from an
event dispatched by GDK(if the module is loaded via GtkSettings) or be
called directly without entering the GDK
