Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!bingvaxu!sunybcs!ugkamins
From: ugkamins@sunybcs.uucp (John Kaminski)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Intuition bug in ActivateWindow???
Message-ID: <5438@cs.Buffalo.EDU>
Date: 24 Apr 89 03:40:08 GMT
References: <11640017@hpfcdc.HP.COM>
Sender: nobody@cs.Buffalo.EDU
Reply-To: ugkamins@sunybcs.UUCP (John Kaminski)
Organization: SUNY/Buffalo Computer Science
Lines: 14

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?

---
a-WYSIWYG, a-WYSIWIG
a-WYSIWYG, a-WYSIWIG
a-WYSIWYG, a-WYSIWIG
a-WYSIWYG, a-WYSIWIG
In the jungle
The silicon jungle
The process sleeps tonight