X-Git-Url: http://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_getyx.3x.html;h=7f098479241199faacc310053affb7bf2063ea5a;hp=994e0f7f0abe5da2f67710192c8560d9b228d664;hb=HEAD;hpb=e5d1530ca229aef94a3c84ad33f8ae89f35c4045 diff --git a/doc/html/man/curs_getyx.3x.html b/doc/html/man/curs_getyx.3x.html index 994e0f7f..18571700 100644 --- a/doc/html/man/curs_getyx.3x.html +++ b/doc/html/man/curs_getyx.3x.html @@ -1,6 +1,6 @@ -
--curs_getyx(3x) curs_getyx(3x) +curs_getyx(3x) Library calls 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> - 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. - 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.
@@ -78,29 +78,30 @@
- All of these interfaces are macros. A "&" is not necessary before the + 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 - XSI Curses standard, Issue 4. + The getyx, getparyx, getbegyx and getmaxyx macros are described in + X/Open Curses, Issue 4. This implementation also provides functions getbegx, getbegy, getcurx, getcury, getmaxx, getmaxy, getparx and getpary for compatibility with - older versions of curses. + older versions of curses; see curs_legacy(3x). - 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. + example, the WINDOW._maxx and WINDOW._maxy values in ncurses have (at + least since release 1.8.1) differed by one from some other + implementations. The difference is hidden by means of the macro + getmaxyx.
@@ -108,7 +109,7 @@ - curs_getyx(3x) +ncurses 6.5 2024-04-20 curs_getyx(3x)