X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_getyx.3x.html;h=f3bc2424463bc52b9718a2be8b2ecdf7918cf72d;hp=c734eca81184cc885c12f2f8abb68191ceff4430;hb=9f479192e3ca3413d235c66bf058f8cc63764898;hpb=bca50d0d8592defee6c584fdedd25f4b1a31345b diff --git a/doc/html/man/curs_getyx.3x.html b/doc/html/man/curs_getyx.3x.html index c734eca8..f3bc2424 100644 --- a/doc/html/man/curs_getyx.3x.html +++ b/doc/html/man/curs_getyx.3x.html @@ -1,6 +1,7 @@ -
--curs_getyx(3x) curs_getyx(3x) +curs_getyx(3X) curs_getyx(3X)
- getyx, getparyx, getbegyx, getmaxyx - get curses cursor and window + getyx, getparyx, getbegyx, getmaxyx - get curses cursor and window coordinates
- #include <curses.h> + #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); + 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);
- The getyx macro places the current cursor position of the given window - in the two integer variables y and x. + 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 beginning coordi- - nates of the subwindow relative to the parent window into two integer - variables y and x. Otherwise, -1 is placed into y and x. + If win is a subwindow, the getparyx macro places the beginning + 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 begin- - ning coordinates and size of the specified window. + Like getyx, the getbegyx and getmaxyx macros store the current + beginning coordinates and size of the specified window.
@@ -77,37 +78,38 @@
- All of these interfaces are macros. A "&" is not necessary before the - variables y and x. + All of these interfaces are macros. A "&" is not necessary before the + variables y and x.
- The getyx, getparyx, getbegyx and getmaxyx macros are described in the + The getyx, getparyx, getbegyx and getmaxyx macros are described in the XSI Curses standard, Issue 4. - This implementation also provides functions getbegx, getbegy, getcurx, - getcury, getmaxx, getmaxy, getparx and getpary for compatibility with + This implementation also provides functions getbegx, getbegy, getcurx, + getcury, getmaxx, getmaxy, getparx and getpary for compatibility with older versions of curses. - Although X/Open Curses does not address this, many implementations pro- - vide members of the WINDOW structure containing values corresponding to - these macros. For best portability, do not rely on using the data in - WINDOW, since some implementations make WINDOW opaque (do not allow + Although X/Open Curses does not address this, many implementations + provide members of the WINDOW structure containing values corresponding + to these macros. For best portability, do not rely on using the data + in WINDOW, since some implementations make WINDOW opaque (do not allow direct use of its members). Besides the problem of opaque structures, the data stored in like-named members may not have like-values in different implementations. For example, the WINDOW._maxx and WINDOW._maxy values in ncurses have (at - least since release 1.8.1) differed by one from some other implementa- - tions. The difference is hidden by means of the macro getmaxyx. + least since release 1.8.1) differed by one from some other + implementations. The difference is hidden by means of the macro + getmaxyx.
- curses(3x), curs_legacy(3x), curs_opaque(3x) + curses(3X), curs_legacy(3X), curs_opaque(3X) - curs_getyx(3x) + curs_getyx(3X)