Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!hpfcdc!cunniff
From: cunniff@hpfcdc.HP.COM (Ross Cunniff)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Intuition bug in ActivateWindow???
Message-ID: <11640019@hpfcdc.HP.COM>
Date: 24 Apr 89 15:17:04 GMT
References: <11640017@hpfcdc.HP.COM>
Organization: HP Ft. Collins, Co.
Lines: 15

> The original post dealt with howcome ActivateWindow() does strange things.
> in both the algorithm in the explanation and the source code itself, the
> WorkBench screen is closed and THEN the custom screen is opened.  Is that
> going to be kosher with the system?  Shouldn't those two steps be in
> transposed order?

It doesn't matter.  The behavior is exhibited if CloseWorkBench() occurs
after OpenScreen().  It is kinda desirable to CloseWorkBench BEFORE
OpenScreen(), to reduce memory fragmentation.


				Ross Cunniff
				Hewlett-Packard Colorado Languages Lab
				...{ucbvax,hplabs}!hpfcla!cunniff
				cunniff%hpfcrt@hplabs.HP.COM