Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!brutus.cs.uiuc.edu!wuarchive!texbell!texsun!newstop!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Open a console window from Lattice
Message-ID: <129114@sun.Eng.Sun.COM>
Date: 12 Dec 89 19:00:54 GMT
References: <129043@sun.Eng.Sun.COM> <812@jc3b21.UUCP>
Sender: news@sun.Eng.Sun.COM
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 19

In article <812@jc3b21.UUCP> fgd3@jc3b21.UUCP (Fabbian G. Dufoe) writes:
[Excellent description of how to attach a console device to a window deleted]
>     Well, maybe it's not so straightforward after all.  But doing it isn't
>the hard part.  The hard part is finding out how to do it.  THE AMIGA
>REALLY NEEDS BETTER DOCUMENTATION!

I was answering the question of "How do I attach a CON: stream to my
window." Which is decidedly more difficult. Attaching the console.device
gives you the ability to send and receive IO requests to the window/keyboard
but the CON: lets you use the stdio library of C and that can be a feature.

I agree about the need for better documentation, but it's coming. The new
Hardware manual it pretty whizzy and the new IntuiExecGraphiLib book should
be an improvement as well.

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@Eng.Sun.COM
These opinions are my own and no one elses, but you knew that didn't you.
"If it didn't have bones in it, it wouldn't be crunchy now would it?!"