Re: Multiple threads and gtk_main()

2007-07-11 Thread Chris Vine
On Wed, 2007-07-11 at 22:06 +0100, Chris Vine wrote: > On Wed, 2007-07-11 at 08:59 +0200, Jonathan Winterflood wrote: > > Hi, > > > > Could the GAsyncQueue be configured to run a callback in the main > > thread when a element (or whatever gets pushed into it) is ready, just > > like one woud do wi

Re: Multiple threads and gtk_main()

2007-07-11 Thread Chris Vine
On Wed, 2007-07-11 at 08:59 +0200, Jonathan Winterflood wrote: > Hi, > > Could the GAsyncQueue be configured to run a callback in the main > thread when a element (or whatever gets pushed into it) is ready, just > like one woud do with a GIOChannel ? > > It would be cleaner than a timeout or an i

Re: Multiple threads and gtk_main()

2007-07-11 Thread Dong Luo
I'm new to gtk and still reading tutorials, but can we register a new signal to any global object (possiblely main window), thus call back function can be connected in the main thread and the signal can be emitted in other threads? --- Jonathan Winterflood <[EMAIL PROTECTED]> wrote: > On 7/11/07,

Re: Multiple threads and gtk_main()

2007-07-11 Thread Gabriele Greco
Eduardo M KALINOWSKI wrote: > Make your threads add stuff to a single GAsyncQueue. Let an idle > function (or a timeout function) always run, that checks the GAsyncQueue > and does something if there is something to do, or simply returns if it > is empty. Wouldn't that work? > Yes, but that w

Re: Multiple threads and gtk_main()

2007-07-11 Thread Jonathan Winterflood
On 7/11/07, Gabriele Greco <[EMAIL PROTECTED]> wrote: > > Jonathan Winterflood wrote: > > Could the GAsyncQueue be configured to run a callback in the main thread > > when a element (or whatever gets pushed into it) is ready, just like one > > woud do with a GIOChannel ? > > > > It would be cleaner

Re: Multiple threads and gtk_main()

2007-07-10 Thread Jonathan Winterflood
Hi, Could the GAsyncQueue be configured to run a callback in the main thread when a element (or whatever gets pushed into it) is ready, just like one woud do with a GIOChannel ? It would be cleaner than a timeout or an idle function I think. Jonathan On 7/10/07, Chris Vine <[EMAIL PROTECTED]> w

Re: Multiple threads and gtk_main()

2007-07-10 Thread Chris Vine
On Tue, 2007-07-10 at 13:10 -0300, Eduardo M KALINOWSKI wrote: [snip] > Make your threads add stuff to a single GAsyncQueue. Let an idle > function (or a timeout function) always run, that checks the GAsyncQueue > and does something if there is something to do, or simply returns if it > is empty

Re: Multiple threads and gtk_main()

2007-07-10 Thread wallace . owen
On Tue, 2007-07-10 at 17:44 +0200, Gabriele Greco wrote: > I've a few threads (more than one) doing some work (not accessing GTK > functions), I'd like to have a general way to make them notify their > work to the main loop. > > I used the g_idle_add() in the previous context where I had only a

Re: Multiple threads and gtk_main()

2007-07-10 Thread Eduardo M KALINOWSKI
Gabriele Greco escreveu: > I've a few threads (more than one) doing some work (not accessing GTK > functions), I'd like to have a general way to make them notify their > work to the main loop. > > I used the g_idle_add() in the previous context where I had only a > thread with this behaviour, bu