icon Top 9 categories map      RocketAware > man pages >


Tips: Browse or Search all pages for efficient awareness of more than 6000 of the most popular reusable and open source applications, functions, libraries, and FAQs.

The "RKT couplings" below include links to source code, updates, additional information, advice, FAQs, and overviews.


Search all pages


By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Integer, Floating point, Matrix, Statistics, Boolean, ...

Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...


RocketLink!--> Man page versions: OpenBSD FreeBSD Others

curs_refresh(3)                                   curs_refresh(3)

       refresh, wrefresh, wnoutrefresh, doupdate, redrawwin, wre-
       drawln - refresh curses windows and lines

       #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);

       The refresh and wrefresh  routines  (or  wnoutrefresh  and
       doupdate)  must be called to get actual output to the ter-
       minal, as other routines  merely  manipulate  data  struc-
       tures.   The  routine  wrefresh copies the named window to
       the physical terminal screen, taking into account what  is
       already  there  in order to do optimizations.  The refresh
       routine is the same, using stdscr as the  default  window.
       Unless  leaveok  has  been enabled, the physical cursor of
       the terminal is left at the location  of  the  cursor  for
       that window.

       The  wnoutrefresh  and  doupdate  routines  allow multiple
       updates with more  efficiency  than  wrefresh  alone.   In
       addition  to  all  the window structures, curses keeps two
       data structures representing the terminal screen: a physi-
       cal screen, describing what is actually on the screen, and
       a virtual screen, describing what the programmer wants  to
       have on the screen.

       The  routine wrefresh works by first calling wnoutrefresh,
       which copies the named window to the virtual  screen,  and
       then  calling  doupdate, which compares the virtual screen
       to the physical screen and does the actual update.  If the
       programmer  wishes  to  output  several windows at once, a
       series of calls to wrefresh results in  alternating  calls
       to  wnoutrefresh  and  doupdate, causing several bursts of
       output to the screen.  By first calling  wnoutrefresh  for
       each  window,  it  is then possible to call doupdate once,
       resulting in only one burst of output,  with  fewer  total
       characters transmitted and less CPU time used.  If the win
       argument to wrefresh is 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 overlap-
       ping windows; it means that if two  windows  overlap,  you
       can  refresh  them  in either order and the overlap region


curs_refresh(3)                                   curs_refresh(3)

       will be modified only when it is explicitly changed.  (But
       see  the  section on PORTABILITY below for a warning about
       exploiting this behavior.)

       The wredrawln routine indicates to curses that some screen
       lines  are corrupted and should be thrown away before any-
       thing is written over  them.   It  touches  the  indicated
       lines  (marking  them  changed).   The routine redrawwin()
       touches the entire window.

       Routines that return an integer return ERR  upon  failure,
       and  OK  (SVr4 only specifies "an integer value other than
       ERR") upon successful completion.

       Note that refresh and redrawwin may be macros.

       The XSI Curses standard, Issue  4  describes  these  func-

       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.

       curses(3), curs_outopts(3)


Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.

(Corrections, notes, and links courtesy of RocketAware.com)

[Detailed Topics]
FreeBSD Sources for curs_refresh(3) functions
OpenBSD sources for curs_refresh(3)

[Overview Topics]

Up to: Curses - Curses (Library for text display interfaces)

RocketLink!--> Man page versions: OpenBSD FreeBSD Others

Rapid-Links: Search | About | Comments | Submit Path: RocketAware > man pages > curs_refresh.3/
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments