>> I just wondered why so many current programms are using these functions
>> this technique is consedered obsolete.
> curses is oriented to full-screen programs (and normally clears the
> initialization), while some applications use the same information for
> like command-line editing, not full-screen. In those cases, there's
> little incentive to change from termcap to terminfo (though recently
> pointed out that the legacy interface for tgetent is broken in the latest
> - HPUX 11.x for instance - making it undesirable to use termcap on those
OK, thank you Thomas!
So it seems it is quite "legal" to use ;-)
I must admit that I am only in the beginning of understanding this whole
I stumbled across ncurses for my first application in C++ as I needed some
control over screen output (nload,
http://www.roland-riegel.de/nload/index_en.html, displays network traffic).
I noticed that after finishing my program in xterm the console was
restored, but not after using it in a non-xterm shell.
Normally this wouldn't bother me at all, but I have included a command line
switch for only displaying the provided information once and immediatly
exiting. But if the screen is cleared after the exit, this has no sense at
SuSE Linux 7.2 (i386)
Registered Linux user #214199 (see http://counter.li.org)