functions in curses.i -
|
caddch
|
caddch | |
| SEE | cprintw | |
|
ccbreak
|
ccbreak | |
| SEE | cendwin | |
|
cclear
|
cclear | |
| SEE | cerase | |
|
cclearok
|
cclearok | |
| SEE | cscrollok | |
|
cclrtobot
|
cclrtobot | |
| SEE | cerase | |
|
cclrtoeol
|
cclrtoeol | |
| SEE | cerase | |
|
ccurs_move
|
ccurs_move | |
| SEE | cgetlines | |
|
ccurs_set
|
ccurs_set | |
| SEE | cgetlines | |
|
cecho
|
cecho | |
| SEE | cflash | |
|
cgetch
|
cgetch | |
| SEE | kbdinit | |
|
cgetcols
|
cgetcols | |
| SEE | cgetlines | |
|
cgetstr
|
cgetstr | |
| SEE | cflash | |
|
cidlok
|
cidlok | |
| SEE | cscrollok | |
|
cisendwin
|
cisendwin | |
| SEE | cendwin | |
|
ckeypad
|
ckeypad | |
| SEE | cnodelay | |
|
cleaveok
|
cleaveok | |
| SEE | cscrollok | |
|
cmeta
|
cmeta | |
| SEE | cnodelay | |
|
cmvprintw
|
cmvprintw | |
| SEE | cprintw | |
|
cnl
|
cnl | |
| SEE | craw | |
|
cnocbreak
|
cnocbreak | |
| SEE | cendwin | |
|
cnoecho
|
cnoecho | |
| SEE | cflash | |
|
cnoraw
|
cnoraw | |
| SEE | craw | |
|
cnotimeout
|
cnotimeout | |
| SEE | cnodelay | |
|
countdown
|
func countdown(sec,interval)
sec: number of seconds to coundown
interval: time to pause between refresh, in ms
| |
| SEE ALSO: | ||
|
crefresh
|
crefresh | |
| SEE | cprintw | |
|
ctimeout
|
ctimeout | |
| SEE | craw | |
|
curses{}
|
curses package
The curses plugin wraps some of the curses routine, hopefully enough
of them to do something useful in a one terminal environment (i.e.
I did not wrap multi-terminal curses control routines like newterm).
Curses allow control of the screen and keyboard in a unbuffered way.
you can position and write string wherever you want, without or with
scroll, and you can monitor keyboard events. This can be useful to
report results of large computations without the rapid screen scrolling
and/or steer simulations as they go.
You can see examples of use in the check-plug.i file or in the
"progressbar" or "countdown" routines below.
NOTE: This routine uses the "curses" library. Thus, it will work
on Linux and maxosx machines (and probably unix) but *NOT* on windows
machine (unless curses has been ported to windows, which I am ignorant
of).
Also, curses may not have all the term files. In particular, I have
noticed that it doesn't like to be ran in an emacs terminal/environment.
| |
| SEE ALSO: | ||
|
kbd
|
kbd | |
| SEE | kbdinit | |
|
kbdend
|
kbdend | |
| SEE | kbdinit | |
|
progressbar
|
print out a progress bar in the terminal using curse
no init necessary. Just do a tic(counter) at the start of the loop.
term has to be in curse mode.
| |
| SEE ALSO: | ||