Lines Matching refs:screen
118 screen-painting and input-event handling which presents a high level
119 screen model to the programmer, hiding differences between terminal
120 types and doing automatic optimization of output to change one screen
137 provide screen-handling for the vi editor; these used the termcap
173 * Support for multiple screen highlights (BSD curses could only
178 * Support for pads (windows of larger than screen size on which the
179 screen or a subwindow defines a viewport).
185 even on terminals that leave "magic cookies" on the screen to mark
217 A data structure describing a sub-rectangle of the screen
218 (possibly the entire screen). You can write to a window as
219 though it were a miniature screen, scrolling independently of
220 other windows on the physical screen.
223 A subset of windows which are as large as the terminal screen,
228 terminal screen
230 like, i.e., what the user sees now. This is a special screen.
242 at the top of the program source. The screen package uses the Standard
252 In order to update the screen optimally, it is necessary for the
253 routines to know what the screen currently looks like and what the
256 the routines, including its starting position on the screen (the (y,
258 these (called curscr, for current screen) is a screen image of what
259 the terminal currently looks like. Another screen (called stdscr, for
260 standard screen) is provided by default to make changes on.
264 any necessary relation to what is really on the terminal screen; it is
267 To make the section of physical screen corresponding to a window
271 A given physical screen section may be within the scope of any number
276 screen.
287 Many functions are defined to use stdscr as a default screen. For
347 Now we describe how to actually use the screen package. In it, we
416 In order to use the screen package, the routines must know about
429 Once the screen windows have been allocated, you can set them up for
430 your program. If you want to, say, allow a screen to scroll, use
465 screen look like curscr thinks it looks like. This is useful for
466 implementing a command which would redraw the screen in case it get
472 set, will call addch() to echo the character. Since the screen package
501 You can use these to draw boxes and simple graphs on the screen. If
507 The ncurses package supports screen highlights including standout,
513 contents of a screen cell. See the curses.h header file for a complete
573 zero-origin, screen-relative character-cell coordinates of the mouse
627 refresh() will clear the screen. If an error occurs a message
636 modes, move the cursor to the lower left corner of the screen,
639 program will restore the ncurses screen from before the escape.
646 SCREEN variable is not a screen in the sense we are describing
656 previously opened by newterm(). The screen reference for the
671 terminal screen, taking into account what is already there in
680 keeps two data structures representing the terminal screen: a
681 physical screen, describing what is actually on the screen, and
682 a virtual screen, describing what the programmer wants to have
683 on the screen. wrefresh works by first copying the named window
684 to the virtual screen (wnoutrefresh()), and then calling the
685 routine to update the screen (doupdate()). If the programmer
688 doupdate(), causing several bursts of output to the screen. By
698 without setting up the curses screen structures or changing the
771 refresh() call will blow them off the screen. The right way to handle
773 screen with declared windows which you then wnoutrefresh() somewhere
778 screen layouts to use tiled rather than overlapping windows.
795 time in screen mode, but occasionally returns to ordinary "cooked"
800 intending to terminate the program. This will take the screen back to
803 the screen.
806 whether ncurses screen mode is active. It returns TRUE in the interval
815 refresh(); /* restore save modes, repaint screen */
821 followed by an refresh and a screen repaint you code yourself. The
822 refresh will pick up the new screen size from the xterm's environment.
825 curses implementations). Its drawback is that it clears the screen to
829 limited to the new screen dimensions, and pads stdscr with blanks if
830 the screen is larger.
834 calls resizeterm to update the size of the standard screen's window,
837 it cannot know how you want the screen re-painted. You will usually
847 file pointers; each call will return a screen reference, and stdscr
868 Use the addchstr() family of functions for fast screen-painting of
907 To understand why this is a problem, remember that screen updates are
910 to the virtual screen, and then changes are calculated to update the
911 physical screen (and applied to the terminal). But "copied to" is not
918 copies to the virtual screen. Some implementations do "change copy",
921 "entire copy", copying all window locations to the virtual screen
947 when you want a screen update, you do update_panels(), it will do all
983 The ncurses library by itself provides good support for screen
1041 the panel's screen location, contents, and size unchanged.
1050 screen flicker.
1094 A menu is a screen display that assists the user to choose some subset
1135 5. Refresh the screen.
1184 to fit on-screen will result in a menu display that is vertically
1219 these actually modifies the screen. To do that, call wrefresh() or
1288 of on-screen forms for data entry and program control.
1307 segmented into pages; each entry to a new page clears the screen.
1335 5. Refresh the screen.
1366 the screen (the third and fourth arguments, which must be zero or
1371 The fifth argument allows you to specify a number of off-screen rows.
1373 nonzero, the form will be scrollable, with only one screen-full
1375 field dynamic and grow it so it will no longer fit on the screen, the
1458 It is possible to move a field's location on the screen:
1485 the field on the screen, without affecting in any way the data in the
1510 start of a new form screen.
1531 Controls whether the field is visible on the screen. Can be
1840 buffer value reflects on-screen reality, call field_buffer() either
1877 the screen. There is an hidden step before posting, which is the
1880 library associates every form with the full-screen window stdscr.
1883 frame window on your screen display. This can be useful if you want to
1884 adapt the form display to different screen sizes, dynamically tile
1885 forms on the screen, or use a form as part of an interface layout
1930 field is multi-line and there is data off-screen below it.
1933 character position is off-screen (not being displayed).
1963 display of a new form screen.
2029 in screen-position order, so the sequence goes left-to-right and