Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!caip!cbmvax!higgin
From: higgin@cbmvax.cbm.UUCP (Paul Higginbottom)
Newsgroups: net.micro.amiga
Subject: Re: Terminal program -- HELP!!!!!
Message-ID: <253@cbmvax.cbmvax.cbm.UUCP>
Date: Fri, 16-May-86 12:44:04 EDT
Article-I.D.: cbmvax.253
Posted: Fri May 16 12:44:04 1986
Date-Received: Sun, 18-May-86 13:08:01 EDT
References: <1781@gitpyr.UUCP>
Reply-To: higgin@cbmvax.UUCP (Paul Higginbottom)
Organization: Commodore Technology, West Chester, PA
Lines: 31

In article <1781@gitpyr.UUCP> wutka@gitpyr.UUCP (Mark Wutka) writes:
>
>  I have cooked up a pretty nice terminal program...
>and right now the way it does IO is slow...it does requests
>for one character at a time. I think if I check to see how many characters
>are there I can save alot of time...
>

---
Thought I'd comment on this... making your screen 1 bit plane will speed up
console output, and yes, putting a request off fora ton of characters and
then seeing how many are in there is MUCH faster.

>I seem to have a very weird problem...it occurs when my program receives
>a NULL through the serial port...
>if my program gets a NULL,
>the keyboard locks up and I can't close the window...
>with the window stuff is messed up...

I would guess your program's never getting back to the loop to wait for more
IDCMP's once you get a NULL, hence no opportunity to act on CLOSEWINDOW or
RAWKEY anymore.  If you're handling things on a string basis, you're in
trouble because a null will terminate it of course.  Thus, I hope you're not
doing strlen()'s of input buffers or anything.  Make sure you're parsing
characters one at a time always and perhaps printing out something when you
receive a null and then ignoring it might help you.

	Hope this helps,
		Paul Higginbottom

Disclaimer: I do not work for Commodore and my opinions are at least my own.