Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!unido!fauern!tumuc!lan!rommel
From: rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel)
Newsgroups: comp.os.os2
Subject: Re: uEMACS
Message-ID: <1020@tuminfo1.lan.informatik.tu-muenchen.dbp.de>
Date: 2 Jan 90 12:46:36 GMT
References: <5345@udccvax1.acs.udel.EDU> <976@tuminfo1.lan.informatik.tu-muenchen.dbp.de> <1654.2590d3f4@cc.helsinki.fi>
Sender: news@lan.informatik.tu-muenchen.dbp.de
Reply-To: rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel)
Organization: Inst. fuer Informatik, TU Muenchen, W. Germany
Lines: 11


I know about the busy loop problem. But I already tried to use to
separate threads for keyboard and mouse input. I was surprised to see
that the MouReadEventQueue() call apears to use busy wait too when the
MOUSE_WAIT mode is used. When my mouse thread waited for an event, my
other thread waiting for keyboard input was blocked !?! Any hints ?
Currently I use the MOUSE_NOWAIT mode and make some DosSleep() calls
between the MouReadEventQueue() calls.

Kai Uwe Rommel
rommel@lan.informatik.tu-muenchen.dbp.de