On Sun, 2007-08-05 at 20:11 +0800, Gregory Hosler wrote:
> Your example clears up alot of stuff for me. One of my questions (that your
> example pretty much clarifies for me), was "what do I g_idle_add()" ?
> If I understand correctly, you basically add callback functions, and in
> particular, ones
On Sat, 2007-08-04 at 22:07 +0800, Gregory Hosler wrote:
> That threads_enter/threads_leave doesn't look so bad, since I'm not
> doing a lot of gtk withing my thread. Looks like it might be the way
> to go for me.
Beware that you need to ensure that you call gdk_threads_enter() before
calling gtk_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gabriel Schulhof wrote:
> On Sun, 2007-08-05 at 11:29 +0800, Gregory Hosler wrote:
>> I'm looking for code examples specifically on how to use/implement
>> g_idle_add().
>> Know any projects that uses g_idle_add() and related infrastructure?
>
>
> s
On Sun, 2007-08-05 at 11:24 +0800, Gregory Hosler wrote:
> The main loop is already protected (by threads_enter()/threads_leave() so I
> didn't need to add any code at all to the main code (and I don't have any
> timeout callbacks either), so the only places I needed to add the
> threads_enter/lea
On Sun, 2007-08-05 at 11:29 +0800, Gregory Hosler wrote:
> I'm looking for code examples specifically on how to use/implement
> g_idle_add().
> Know any projects that uses g_idle_add() and related infrastructure?
static gboolean
make_insensitive_idle_cb(gpointer data)
{
GtkWidget *widget = GTK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian J. Tarricone wrote:
> On Sat, 04 Aug 2007 22:50:06 +0100 Chris Vine wrote:
>
>> On Sat, 2007-08-04 at 22:07 +0800, Gregory Hosler wrote:
>>> That threads_enter/threads_leave doesn't look so bad, since I'm not
>>> doing alot of gtk withing my thr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Vine wrote:
> On Sat, 2007-08-04 at 22:07 +0800, Gregory Hosler wrote:
>> That threads_enter/threads_leave doesn't look so bad, since I'm not doing
>> alot
>> of gtk withing my thread. Looks like it might be the way to go for me.
>
> You may be
On Sat, 04 Aug 2007 22:50:06 +0100 Chris Vine wrote:
> On Sat, 2007-08-04 at 22:07 +0800, Gregory Hosler wrote:
> > That threads_enter/threads_leave doesn't look so bad, since I'm not
> > doing alot of gtk withing my thread. Looks like it might be the way
> > to go for me.
>
> You may be missing
On Sat, 2007-08-04 at 22:07 +0800, Gregory Hosler wrote:
> That threads_enter/threads_leave doesn't look so bad, since I'm not doing alot
> of gtk withing my thread. Looks like it might be the way to go for me.
You may be missing the point. If you access GTK+ from more than one
thread, then all o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Ne?as (Yeti) wrote:
> On Sat, Aug 04, 2007 at 09:38:25PM +0800, Gregory Hosler wrote:
>> I have a threaded gtk application. The threads create some gui (gtk
>> widgets/windows). and most of the time (maybe 80%) everything works as
>> expected.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Ne?as (Yeti) wrote:
> On Sat, Aug 04, 2007 at 09:38:25PM +0800, Gregory Hosler wrote:
>> I have a threaded gtk application. The threads create some gui (gtk
>> widgets/windows). and most of the time (maybe 80%) everything works as
>> expected.
>
On Sat, Aug 04, 2007 at 09:38:25PM +0800, Gregory Hosler wrote:
> I have a threaded gtk application. The threads create some gui (gtk
> widgets/windows). and most of the time (maybe 80%) everything works as
> expected.
> Occassionally I will get the message on stdout
>
> Xlib: unexpected as
12 matches
Mail list logo