Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!cbnewsc!straka
From: straka@cbnewsc.att.com (richard.j.straka)
Newsgroups: comp.sys.mac.apps
Subject: Re: WORD 4.0 with AfterDark and MultiFinder
Message-ID: <1991Feb21.142759.24626@cbnewsc.att.com>
Date: 21 Feb 91 14:27:59 GMT
References: <1991Feb20.021041.4242@mentorg.com>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 28

In article <1991Feb20.021041.4242@mentorg.com> bruceh@mentorg.com (Bruce Holm) writes:
:Under Multifinder, I boot MS Word 4.0.  I also have the INIT called
:After Dark v2.x. If I type in a bunch of stuff (not sure this is a
:requirement to see this problem) and then go off and do something else
:(not on the computer), AD then takes over and saves my screen.  Some
:time later (10+ minutes) I come back and try to do something in the
:Word session.  Nothing happens.  At first I though that the machine
:had hung but if I click the mouse a bunch (cursor does respond to
:mouse movement) after a while (a minute or so) the application finally
:wakes up and plays the queued up events that I did trying to wake it
:up.
:
:Has anyone else seen this strange behavior?

I have found that sending the mouse into the sleep corner, and then back out
(or just typing in the password again) usually seems to get word to wake up.

Interestingly, any mouse clicks or typing while Word was "asleep" then seem
to get processed after Word wakes up.

And, yes, it seems that Word is the only application that has a problem with
After Dark (Word also has some incompatibilities with AltWDEF, Front+Center,
..., so I'm NOT surprised).  What a hack.
-- 
Richard Straka                    AT&T Bell Laboratories, IH-6K311
---------------------------------------------------------------------------
UUCP:     att!ihlpf!straka        MSDOS: All the wonderfully arcane
INTERNET: straka@att.ATT.COM      syntax of UNIX(R), but without the power.