My audio-recorder that was based on GTK2 had some threads that also
modified the GUI-elements. I had to call
GDK_THREADS_ENTERhttps://developer.gnome.org/gdk3/3.10/gdk3-Threads.html#GDK-THREADS-ENTER:CAPS
/
On Thu, 28 Nov 2013 09:11:45 +
Osmo Antero osm...@gmail.com wrote:
My audio-recorder that was based on GTK2 had some threads that also
modified the GUI-elements. I had to call
GDK_THREADS_ENTERhttps://developer.gnome.org/gdk3/3.10/gdk3-Threads.html#GDK-THREADS-ENTER:CAPS
/
On Wed, 27 Nov 2013 19:32:26 -0800 (PST)
David Buchan pdbuc...@yahoo.com wrote:
I removed the call to g_thread_init() and it still works fine! Great
catch there.
You can include it with glib = 2.32 - it is a no-op then. You should
include it if you want your code to be able to run on earlier
Hi
i have a problem with GTK application. I create a Gtk.Socket within my
application and embed an urxvt terminal inside it(urxvt can embed itself into
provided window id, which i get from socket.get_id()) .. but now i want to
catch signal of mouse event in this embedded window and im not able
On Wed, 27 Nov 2013 19:32:26 -0800 (PST)
David Buchan pdbuc...@yahoo.com wrote:
I removed the call to g_thread_init() and it still works fine! Great
catch there.
You can include it with glib = 2.32 - it is a no-op then. You should
include it if you want your code to be able to run on earlier
hi;
On 28 November 2013 11:09, Chris Vine ch...@cvine.freeserve.co.uk wrote:
By the way, why not have your idle function return FALSE instead of
EXIT_SUCCESS? Both evaluate to 0, but returning FALSE is clearer.
EXIT_SUCCESS is a macro intended to provide a process return value
indicating
On Thu, 28 Nov 2013 14:17:00 +
Emmanuele Bassi eba...@gmail.com wrote:
GSourceFunc functions should return G_SOURCE_CONTINUE or
G_SOURCE_REMOVE; those are aliases for boolean values, but are much,
much clearer to read.
I suggest you put a bug in bugzilla. The documentation for the main
