Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!nrl-cmf!ames!pasteur!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re:  DMouse
Message-ID: <8810020215.AA23368@cory.Berkeley.EDU>
Date: 2 Oct 88 02:15:19 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 24

C86.M-KARLSSON@XNS.Liuida.Seismo (Mikael Karlsson) Writes:
:I love DMouse too, but...
:
:DMouse makes a big no-no when trying to change the active window.
:The offending sequence of commands is:
:Forbid();
:ActivateWindow();
:Permit();
:
:This results in a great lock-up if somebody else (read "me") has 
:performed LockLayers(). ActivateWindow is waiting for me to Unlock
:the layers but since I am an input handler (actually, it's my program
:that is an input handler) I won't get the proper input event since
:DMouse is blocking the input. The conclusion is that ANY program that
:locks the layers will cause DMouse to lock the input handling if 
:the mouse is moved to another window.

	I'm sorry, you are wrong.  The original DMouse *did* do that,
you obviously have a VERY OLD version.  I moved all the intuition stuff to
a process.  In the last couple of versions, the input handler has done 
nothing more than call AllocMem() and send simple messages to the process
to do the more complex operations.  Gee, that was easy!

				-Matt