Newsgroups: comp.os.msdos.programmer
Path: utzoo!utgpu!watserv1!maytag!watstat.waterloo.edu!dmurdoch
From: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Subject: Re: TD 2.01 versus Desqview
Message-ID: <1991Feb5.214639.16061@maytag.waterloo.edu>
Sender: daemon@maytag.waterloo.edu (Admin)
Organization: University of Waterloo
References: <1991Feb4.195510.8883@maytag.waterloo.edu> <656@sun4dts.dts.ine.philips.nl>
Date: Tue, 5 Feb 91 21:46:39 GMT
Lines: 18

In article <656@sun4dts.dts.ine.philips.nl> derek@sun4dts.dts.ine.philips.nl (derek) writes:
>dmurdoch@watstat.waterloo.edu (Duncan Murdoch) writes:
>
>
>	A nicer alternative would be a way to tell Desqview that it should handle
>	the mouse again.  As it is, once a window takes over the mouse, there
>	appears to be no way to give it back to DV.  Does anyone know of one?
>	(I've tried simply saving the mouse state and restoring it later,
>	but it doesn't seem to work.)
>
>Doesn't [R]econfigure [T]une performance F1 (restore mouse) work? If so, 

No, it doesn't work for me.  Once the mouse is gone, it's gone.  (By the
way, can you find that option anywhere in the manual?  I'd like to know
what it's supposed to do.)

Duncan Murdoch