X-Git-Url: http://ncurses.scripts.mit.edu/?a=blobdiff_plain;f=doc%2Fhtml%2Fncurses-intro.html;h=bf56ddeee168cc7aeb96cb6e439fcef04f01a942;hb=ca5fdd32fd43d84fe3d720cd5c07fba28fc506a4;hp=05c756e0e8b4474eb84fb8309af8c22868166e8f;hpb=b1f61d9f3aa244512045a6b02e759825d7049d34;p=ncurses.git diff --git a/doc/html/ncurses-intro.html b/doc/html/ncurses-intro.html index 05c756e0..bf56ddee 100644 --- a/doc/html/ncurses-intro.html +++ b/doc/html/ncurses-intro.html @@ -1,11 +1,39 @@
@@ -613,6 +636,7 @@ Presently, mouse event reporting works in the following environments:
gpm
(1), Alessandro
Rubini's mouse server.
+
@@ -690,7 +714,7 @@ the first call to refresh()
will clear the screen. If an error
occurs a message is written to standard error and the program
exits. Otherwise it returns a pointer to stdscr. A few functions may be
called before initscr (slk_init()
, filter()
,
-ripofflines()
, use_env()
, and, if you are using multiple
+ripoffline()
, use_env()
, and, if you are using multiple
terminals, newterm()
.)
endwin()
endwin()
before exiting or
@@ -704,7 +728,11 @@ restore the ncurses screen from before the escape.
newterm()
instead of initscr()
. newterm()
should
be called once for each terminal. It returns a variable of type
SCREEN *
which should be saved as a reference to that
-terminal. The arguments are the type of the terminal (a string) and
+terminal.
+(NOTE: a SCREEN variable is not a screen in the sense we
+are describing in this introduction, but a collection of
+parameters used to assist in optimizing the display.)
+The arguments are the type of the terminal (a string) and
FILE
pointers for the output and input of the terminal. If
type is NULL then the environment variable $TERM
is used.
endwin()
should called once at wrapup time for each terminal
@@ -728,7 +756,7 @@ the terminal, as other routines merely manipulate data
structures. wrefresh()
copies the named window to the physical
terminal screen, taking into account what is already
there in order to do optimizations. refresh()
does a
-refresh of stdscr()
. Unless leaveok()
has been
+refresh of stdscr
. Unless leaveok()
has been
enabled, the physical cursor of the terminal is left at the
location of the window's cursor.
doupdate()
and wnoutrefresh(win)
@@ -978,7 +1006,7 @@ on and refresh them, the changes made to the overlapping region under historic
To understand why this is a problem, remember that screen updates are
calculated between two representations of the entire display. The
-documentation says that when you refresh a window, it is first copied to to the
+documentation says that when you refresh a window, it is first copied to the
virtual screen, and then changes are calculated to update the physical screen
(and applied to the terminal). But "copied to" is not very specific, and
subtle differences in how copying works can produce different behaviors in the
@@ -1016,7 +1044,7 @@ guarantee an entire-contents copy anywhere.
The really clean way to handle this is to use the panels library. If,
when you want a screen update, you do update_panels()
, it will
-do all the necessary wnoutrfresh()
calls for whatever panel
+do all the necessary wnoutrefresh()
calls for whatever panel
stacking order you have defined. Then you can do one doupdate()
and there will be a single burst of physical I/O that will do
all your updates.
@@ -1218,10 +1246,10 @@ The general flow of control of a menu program looks like this:
curses
.
new_item()
.
new_menu()
.
-menu_post()
.
+post_menu()
.
menu_unpost()
.
+unpost_menu()
.
free_menu()
.
free_item()
.
curses
.
@@ -1304,8 +1332,8 @@ refreshed or erased at post/unpost time. The inner window or
By default, both windows are stdscr
. You can set them with the
functions in menu_win(3x)
.
-When you call menu_post()
, you write the menu to its
-subwindow. When you call menu_unpost()
, you erase the
+When you call post_menu()
, you write the menu to its
+subwindow. When you call unpost_menu()
, you erase the
subwindow, However, neither of these actually modifies the screen. To
do that, call wrefresh()
or some equivalent.
@@ -1437,10 +1465,10 @@ The general flow of control of a form program looks like this:
curses
.
new_field()
.
new_form()
.
-form_post()
.
+post_form()
.
form_unpost()
.
+unpost_form()
.
free_form()
.
free_field()
.
curses
.
@@ -1476,7 +1504,7 @@ the screen (the third and fourth arguments, which must be zero or
greater). Note that these coordinates are relative to the form
subwindow, which will coincide with stdscr
by default but
need not be stdscr
if you've done an explicit
-set_form_window()
call.
+set_form_win()
call.
The fifth argument allows you to specify a number of off-screen rows. If
this is zero, the entire field will always be displayed. If it is
@@ -2156,7 +2184,7 @@ These requests treat the list as cyclic; that is, REQ_NEXT_PAGE
from the last page goes to the first, and REQ_PREV_PAGE
from
the first page goes to the last.
-
REQ_MOVE_RIGHT
from A will
go to B only if A, B, and C all share the same first line;
otherwise it will skip over B to C.
-REQ_NEW_LINE
as described in Editing Requests. The value of this option is
+href="#fedit">Editing Requests. The value of this option is
ignored on dynamic fields that have not reached their size limit;
these have no last line, so the circumstances for triggering a
REQ_NEXT_FIELD
never arise.
REQ_DEL_PREV
as described in
-Editing Requests.
+Editing Requests.