On Wednesday 13 December 2006 21:52, Philip Boulain wrote:
> On Wed, 2006-12-13 at 21:20 +, Chris Vine wrote:
[snip]
> > I does that by itself. You have probably not called g_thread_init() (or
> > Glib::thread_init()).
>
> Ah, I wondered if it was supposed to.
>
> I haven't, no; my understandi
On Wed, 2006-12-13 at 21:20 +, Chris Vine wrote:
> On Wednesday 13 December 2006 18:05, Philip Boulain wrote:
> > When GTK+ is in its main run loop, blocking on an event, is there a way
> > to awaken/unblock it from some external thread such that it will pay
> > attention to newly-added idle fu
On Wednesday 13 December 2006 18:05, Philip Boulain wrote:
> Hullo,
>
> Short version:
> When GTK+ is in its main run loop, blocking on an event, is there a way
> to awaken/unblock it from some external thread such that it will pay
> attention to newly-added idle functions?
[snip]
I does that b
Hullo,
Short version:
When GTK+ is in its main run loop, blocking on an event, is there a way
to awaken/unblock it from some external thread such that it will pay
attention to newly-added idle functions?
Long version with context:
I have a lovely multithreaded application in C++/GTKmm that I'
