Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!sun-barr!newstop!sun!kilowatt!raz
From: raz%kilowatt@Sun.COM (Steve -Raz- Berry)
Newsgroups: comp.sys.amiga
Subject: Re: CLI window on new screen...
Summary: they is some side affects...
Message-ID: <118890@sun.Eng.Sun.COM>
Date: 1 Aug 89 17:32:04 GMT
References: <[917]un.amiga@tronsbox.UUCP> <7192@microsoft.UUCP>
Sender: news@sun.Eng.Sun.COM
Reply-To: raz@sun.UUCP (Steve -Raz- Berry)
Organization: Sun Microsystems, Mountain View
Lines: 35

In article <7192@microsoft.UUCP> bradch@microsoft.UUCP (Bradford Christian ms1) writes:
>In article <[917]un.amiga@tronsbox.UUCP> tron1@tronsbox.UUCP (HIM) writes:
>>I have been working on this one for a while also ...

>>Can I , by hook or by crook, open or "tansplant) a CLI window onto another
>>screen??????

>>How would I  , Why havent I seen it done????

>>ddsw1!tronsbox!tron1

>I pull a (sleazy?) trick in many of my own programs.  When I create a screen,
>I specify WORKBENCHSCREEN (sp?) instead of CUSTOMSCREEN.  This has several
>desirable effects and no (as yet) undesirable ones.  First off, any new CLIs

I have found a few side affects that arn't necessarily good ones. 

First, try this little trick. When you boot your machine, don't do
a LoadWB. Start your application up, and open a CLI on it (I can do
it by using a DMouse hotkey). Then from this CLI issue a LoadWB. 
Guess what happens? LoadWB looks for the *first* Workbench type
screen and completly takes it over. Completely eats your application.
Forget about tring to kill *your* program after that.

Fun huh?

There can also be some confusion if an application is specificly
looking for the Workbench screen (and instead it finds yours). Most of
the time this is a minor inconvienience more than anything else.


---
Steve -Raz- Berry     Disclaimer: It wasn't me! I was volatilizing my esters.
UUCP: sun!kilowatt!raz                   ARPA: raz%kilowatt.EBay@sun.com
KILOWATT: sun!kilowatt!archive-server    archive-server%kilowatt.EBay@sun.com