Re: Gnome/Gtk and thread safety
- From: Shawn T Amundson <amundson eventloop com>
- To: Arnaud Masson <dev2 iodp com>
- Cc: gtk-devel-list gnome org, Jeroen Benckhuijsen <jfbenck home nl>
- Subject: Re: Gnome/Gtk and thread safety
- Date: Thu, 19 Oct 2000 14:32:36 -0500
On Wed, Oct 18, 2000 at 10:21:43AM +0200, Arnaud Masson wrote:
>
> I have seen sample code in BeOS where you have to lock/unlock a window to
> do simple operation on it... not very nice.
>
Actually, the thread stuff in BeOS is pretty nice. Every toplevel
window runs in it's own thread. If you want to do operations on
that window from outside that thread, you have to do some locking.
Doing that might have it's uses, but is not the common case on BeOS
anyway. It makes more sense to construct and throw around BMessages
telling the window thread what it should do. This allows very nice
thread programming with very little effort keeping track of locks
manually.
Actually, our BeOS port of GDK would have multiple events being
handled at the same time because GDK would send BMessages fast
enough to multiple windows, if I remember correctly.
-Shawn
--
Shawn T. Amundson amundson eventloop com
Research and Development http://www.eventloop.com/
EventLoop, Inc. http://www.snorfle.net/
"The assumption that the universe looks the same in every
direction is clearly not true in reality." - Stephen Hawking
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]