X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_window.3x.html;h=da6219d6d5efbde7d1b00ec1d2d8fd7b756527a9;hp=0b9d2a34eeba1c054719c74316e465f17fb3b5a4;hb=77afe78361875f531dc2bf8d73f2e781c8e76176;hpb=46722468f47c2b77b3987729b4bcf2321cccfd01 diff --git a/doc/html/man/curs_window.3x.html b/doc/html/man/curs_window.3x.html index 0b9d2a34..da6219d6 100644 --- a/doc/html/man/curs_window.3x.html +++ b/doc/html/man/curs_window.3x.html @@ -1,7 +1,7 @@
@@ -40,11 +40,15 @@+curs_window(3x) curs_window(3x) + + +
- newwin, delwin, mvwin, subwin, derwin, mvderwin, dupwin, - wsyncup, syncok, wcursyncup, wsyncdown - create curses + newwin, delwin, mvwin, subwin, derwin, mvderwin, dupwin, + wsyncup, syncok, wcursyncup, wsyncdown - create curses windows @@ -77,9 +81,9 @@ to LINES - begin_y and COLS - begin_x. A new full-screen window is created by calling newwin(0,0,0,0). - Calling delwin deletes the named window, freeing all mem- - ory associated with it (it does not actually erase the - window's screen image). Subwindows must be deleted before + Calling delwin deletes the named window, freeing all memo- + ry associated with it (it does not actually erase the win- + dow's screen image). Subwindows must be deleted before the main window can be deleted. Calling mvwin moves the window so that the upper left-hand @@ -104,10 +108,10 @@ dow orig rather than the screen. There is no difference between the subwindows and the derived windows. - Calling mvderwin moves a derived window (or subwindow) - inside its parent window. The screen-relative parameters - of the window are not changed. This routine is used to - display different parts of the parent window at the same + Calling mvderwin moves a derived window (or subwindow) in- + side its parent window. The screen-relative parameters of + the window are not changed. This routine is used to dis- + play different parts of the parent window at the same physical position on the screen. Calling dupwin creates an exact duplicate of the window @@ -115,8 +119,8 @@ Calling wsyncup touches all locations in ancestors of win that are changed in win. If syncok is called with second - argument TRUE then wsyncup is called automatically when- - ever there is a change in the window. + argument TRUE then wsyncup is called automatically whenev- + er there is a change in the window. The wsyncdown routine touches each location in win that has been touched in any of its ancestor windows. This @@ -130,19 +134,44 @@
- Routines that return an integer return the integer ERR - upon failure and OK (SVr4 only specifies "an integer value + Routines that return an integer return the integer ERR up- + on failure and OK (SVr4 only specifies "an integer value other than ERR") upon successful completion. - delwin returns the integer ERR upon failure and OK upon - successful completion. - Routines that return pointers return NULL on error. + X/Open defines no error conditions. In this implementa- + tion + + delwin + returns an error if the window pointer is + null, or if the window is the parent of anoth- + er window. + + This implementation also maintains a list of + windows, and checks that the pointer passed to + delwin is one that it created, returning an + error if it was not.. + + mvderwin + returns an error if the window pointer is + null, or if some part of the window would be + placed off-screen. + + mvwin + returns an error if the window pointer is + null, or if the window is really a pad, or if + some part of the window would be placed off- + screen. + + syncok + returns an error if the window pointer is + null. +
- If many small changes are made to the window, the wsyncup + If many small changes are made to the window, the wsyncup option could degrade performance. Note that syncok may be a macro. @@ -150,22 +179,22 @@
- The subwindow functions (subwin, derwin, mvderwin, wsyn- - cup, wsyncdown, wcursyncup, syncok) are flaky, incom- - pletely implemented, and not well tested. + The subwindow functions (subwin, derwin, mvderwin, wsyn- + cup, wsyncdown, wcursyncup, syncok) are flaky, incomplete- + ly implemented, and not well tested. - The System V curses documentation is very unclear about + The System V curses documentation is very unclear about what wsyncup and wsyncdown actually do. It seems to imply - that they are only supposed to touch exactly those lines + that they are only supposed to touch exactly those lines that are affected by ancestor changes. The language here, - and the behavior of the curses implementation, is pat- - terned on the XPG4 curses standard. The weaker XPG4 spec + and the behavior of the curses implementation, is pat- + terned on the XPG4 curses standard. The weaker XPG4 spec may result in slower updates.
- The XSI Curses standard, Issue 4 describes these func- + The XSI Curses standard, Issue 4 describes these func- tions. @@ -175,49 +204,7 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + curs_window(3x)