🚀 go-pugleaf

In article <6155@ubc-cs.UUCP>, ballard@cheddar.cc.ubc.ca (Alan Ballard) writes:
> You might try closing the mouse/keyboard handles from another thread, which
> *may* have the effect of causing the waits in the key/mouse threads to abort.
> That works in a similar situation for device monitors.  At least, it works
> with OS/2 1.1; I've had some preliminary indication maybe it doesn't always
> work with 1.2.   

I tried. Does not work. 
>  
> An alternative, of course, is to spawn a separate process to contain the 
> threads that wait on mouse and keyboard, and to have them communicate back
> to the main thread via IPC or shared memory.  Then you can just kill this 
> process and restart it when you want to wait again.

I thought that. Somehow I feel it is overkill for such a simple and basic
task. Separate exe file and all that.


Hannu Kulokari
CC, U of Helsinki

kulokari@cc.helsinki.fi (Internet)
kulokari@finuh (Bitnet)