************************************************************************
In message <Pine.SOL.3.91.960207203531.3897B-100000@clark.net> you said:
> If you look deep into the socket-handling routines in circle, you may
> find an input buffer. If you can find this (I'm not sure if it exists in
> circle, I'm just guessing it works this way), and learn how it works, you
> can check the buffer before it gets passed to the command interpreter,
> and just check for the oldest character (the one that was entered first
> since the last buffer purge).
That won't work. You'd essentially be writting another command interpreter
that gets called before the main command interpreter with no change in the
way it performs. The user still has to hit <cr> on his end to send his
buffer across the network. AFAIK the only way you can handle this situation
is by having the user run a specific client program that handles raw output.
Naved
*********************************************************************
How about setting a flag on the pc, if it is set ON, add a newline
every time a letter is entered...then the get_input() should
think that <enter> has been hit. It will then be on its merry
way to parsing it.... It may be that you specifically have to
toss it out of the get_input() loop via the flag.. It just depends
on where it checks for <newline>
on a slightly similar note: Is there a c/c++ command that makes
your password invis when you type it???
If not, is there a simple trick? :)
Ben Greear
greear@pollux.cs.uga.edu | "More weight." -- The Crucible
| "Son, you got a pantie on yer head."
--Raising Arizona
This archive was generated by hypermail 2b30 : 12/07/00 PST