MirOS Manual: curs_getyx(3), getbegyx(3), getmaxyx(3), getparyx(3), getyx(3)


curs_getyx(3)       UNIX Programmer's Manual        curs_getyx(3)

NAME

     getyx, getparyx, getbegyx, getmaxyx - get curses cursor and
     window coordinates

SYNOPSIS

     #include <curses.h>

     void getyx(WINDOW *win, int y, int x);
     void getparyx(WINDOW *win, int y, int x);
     void getbegyx(WINDOW *win, int y, int x);
     void getmaxyx(WINDOW *win, int y, int x);

DESCRIPTION

     The getyx macro places the current cursor position of the
     given window in the two integer variables y and x.

     If win is a subwindow, the getparyx macro places the begin-
     ning coordinates of the subwindow relative to the parent
     window into two integer variables y and x. Otherwise, -1 is
     placed into y and x.

     Like getyx, the getbegyx and getmaxyx macros store the
     current beginning coordinates and size of the specified win-
     dow.

RETURN VALUE

     The return values of these macros are undefined (i.e., they
     should not be used as the right-hand side of assignment
     statements).

NOTES

     All of these interfaces are macros. A "&" is not necessary
     before the variables y and x.

PORTABILITY

     The getyx, getparyx, getbegyx and getmaxyx functions are
     described in the XSI Curses standard, Issue 4.

     This implementation also provides getbegx, getbegy, getcurx,
     getcury, getmaxx, getmaxy, getparx and getpary for compati-
     bility with older versions of curses.

SEE ALSO

     curses(3)

MirOS BSD #10-current  Printed 03.04.2017                       1

Generated on 2017-04-03 16:26:17 by $MirOS: src/scripts/roff2htm,v 1.88 2017/01/29 00:51:06 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002–2017 The MirOS Project, Germany.
This product includes material provided by mirabilos.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.