Path: utzoo!attcan!uunet!aplcen!samsung!sdd.hp.com!decwrl!ucbvax!hbo.UUCP!bice
From: bice@hbo.UUCP (Brent A. Bice)
Newsgroups: comp.windows.news
Subject: Re: windows in limbo
Message-ID: <9007191727.AA16176@>
Date: 25 Jul 90 08:08:53 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 24


>After a while, the windows go 
>off into limbo.  They are there, but you can't do anything with them.  The 
>children canvases, however, are still active and I can access the menus.

Hmmm...  Are you using the FrameInterests dictionary in the window subclass
to put the interests for your menus on the child canvases in?  If so, perhaps
you are stepping on the Window's interests.  If not, perhaps you are killing
FrameEventMgr somehow??   Try putting in a "dbgbreak" call and look at the
FrameEventMgr variable in your window.  That's the process that handles all
the events for a LiteWindow.  See if it's running still.  You can also
look at the FrameInterests to make sure they are still intact.

   Do the windows go "off into limbo" after a particular sequence of events?
Can you reproduce the problem consistently with the same actions on the
users part???


   Brent Bice
   Applied Computing Systems
   2075 Trinity Drive  Suite Lower Level
   Los Alamos, NM  87544
   Voice:(505) 662-3309             Fax:(505) 662-3518
   bice@atlantis.ees.anl.gov    %  I program, therefore I am.