9 Apr
2010
9 Apr
'10
7:07 p.m.
you want the user's input line to remain intact
instead of being broken into pieces by the output.
This could be even more important in case the
interface is a single line Braille 'display'.
I once had some nice code solving this, but it
was written for my then employer, and I can't
use it in open source projects.
That is a good point. A text based interface is quite an abtraction
of something that has been written to be a GUI which means
debug output may well be useful. Since that does damage the
display, with or without brail, it does beg the question as to whether
it could be 'rewritten'.
It could be done with some IO redirection pipes, suitable code in
the 'raw' IO channel to understand where input came from using
a bit of extra select() in there to bring the channels back together
and apply suitable output depending on where the different CR
were, or that incomplete user input lines were rewritten after
each debug line? And then a bit of NL->CRNL for the raw mode
interface.
Not something I would want to code for a prototype but is
unfortunately something that could better be coded in advance
than bolted on the end?
Nick.
_________________________________________________________________
Hotmail: Free, trusted and rich email service.
https://signup.live.com/signup.aspx?id=60969