[600] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: Making gtk thread-safe
daemon@ATHENA.MIT.EDU (Jay Painter)
Wed Jul 30 23:31:11 1997
Date: Wed, 30 Jul 1997 20:31:32 -0700 (PDT)
From: Jay Painter <jay@a42.com>
To: gtk-list@redhat.com
In-Reply-To: <Pine.LNX.3.96.970730194004.27493O-100000@slow>
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
> Hmm.. this may be a silly question, but why would you create an
> application that had multiple threads using gtk ? I would think the most
> reasonable way to use threads in most programs would be to have one for
> the gui, and others for doing I/O, processing tasks or what have you,
> using IPC between them.
Here's an example of somthing I'm doing that I'd like to use threads for:
In my e-mail client, I have to fill a long list of e-mail messages,
sometime 200-400 messages in a list. This takes about 6-10 seconds on my
Pentium. I would really like to launch a thread to fill the list and run
a status bar, and meanwhile the window kept itself re-painted and
menus/sections responded when clicked (and I want to eat my cake too!!!).
It would also be nice to dedicate a thread which just took care for
certain standard events like redrawing and re-sizing windows, so that
those functions would never be blocked.
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
