higgin@cbmvax.cbm.UUCP (Paul Higginbottom) (05/16/86)
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.
wutka@gitpyr.UUCP (05/21/86)
I have cooked up a pretty nice terminal program that does nice VT-100
emulation (including function keys and keypad). It doesn't support upload
and download 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...but that's not what I'm posting about...
I seem to have a very weird problem...it occurs when my program receives
a NULL through the serial port. I have taken great measures to avoid
printing it just in case that was the problem..but it wasn't...
The symptom of the problem is really odd...if my program gets a NULL,
the keyboard locks up and I can't close the window...like something
with the window stuff is messed up...I do my keyboard input using the
RAWKEY option for the window. I just did a little test by printing a NULL
followed by two lines of text and the lines printed!!! Which means that
the program is still going...just the thing that gets the RAWKEY info
and WINDOWCLOSE has stopped working. I can't understand how a NULL could
cause this...anybody had that kinda problem before ???
--
Mark Wutka
Office of Computing Services
Georgia Institute of Technology
Atlanta, Ga.
...!{akgua,allegra,amd,hplabs,ihnp4,masscomp,ut-ngp}!gatech!gitpyr!wutka
...!{rlgvax,sb1,uf-cgrl,unmvax,ut-sally}!gatech!gitpyr!wutka
Official member of NERDS (NERDS Existing in a Recursively Defined System)