| Main index | Section 3 | 日本語 | Options |
#include <curses.h>int refresh(void); int wrefresh(WINDOW *win); int wnoutrefresh(WINDOW *win); int doupdate(void);
int redrawwin(WINDOW *win); int wredrawln(WINDOW *win, int beg_line, int num_lines);
| &#187; | a physical screen, describing what is actually on the screen, and |
| &#187; | a virtual screen, describing what the programmer wants to have on the screen. |
| &#187; | first calling wnoutrefresh, which copies the named window to the virtual screen, and |
| &#187; | then calling doupdate, which compares the virtual screen to the physical screen and does the actual update. |
If the win argument to wrefresh is the physical screen (i.e., the global variable curscr), the screen is immediately cleared and repainted from scratch.
The phrase copies the named window to the virtual screen above is ambiguous. What actually happens is that all touched (changed) lines in the window are copied to the virtual screen. This affects programs that use overlapping windows; it means that if two windows overlap, you can refresh them in either order and the overlap region will be modified only when it is explicitly changed. (But see the section on PORTABILITY below for a warning about exploiting this behavior.)
X/Open Curses does not specify any error conditions. In this implementation
wnoutrefresh returns an error if the window pointer is null, or if the window is really a pad. wredrawln returns an error if the associated call to touchln returns an error.
Whether wnoutrefresh copies to the virtual screen the entire contents of a window or just its changed portions has never been well-documented in historic curses versions (including SVr4). It might be unwise to rely on either behavior in programs that might have to be linked with other curses implementations. Instead, you can do an explicit touchwin before the wnoutrefresh call to guarantee an entire-contents copy anywhere.
| 2024-04-20 | curs_refresh (3X) | ncurses 6.5 |
| Main index | Section 3 | 日本語 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | A child of 5 could understand this! Fetch me a child of 5. | ” |