X-Git-Url: https://ncurses.scripts.mit.edu/?a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_getyx.3x.html;h=0f463c589350f6e51af3478f8fe05c2b06ccc28b;hb=eb51b1ea1f75a0ec17c9c5937cb28df1e8eeec56;hp=d6db1a8bc745af8e763802c46472a1fcc5bdee1b;hpb=46722468f47c2b77b3987729b4bcf2321cccfd01;p=ncurses.git diff --git a/doc/html/man/curs_getyx.3x.html b/doc/html/man/curs_getyx.3x.html index d6db1a8b..0f463c58 100644 --- a/doc/html/man/curs_getyx.3x.html +++ b/doc/html/man/curs_getyx.3x.html @@ -1,7 +1,7 @@ - - +
+ +- - --
- getyx, getparyx, getbegyx, getmaxyx - get curses cursor - and window coordinates +curs_getyx(3x) curs_getyx(3x) --
- #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); --
- The getyx macro places the current cursor position of the - given window in the two integer variables y and x. +
+ getyx, getparyx, getbegyx, getmaxyx - get curses cursor and window + coordinates - 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. Other- - wise, -1 is placed into y and x. - Like getyx, the getbegyx and getmaxyx macros store the - current beginning coordinates and size of the specified - window. +
+ #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); --
- The return values of these macros are undefined (i.e., - they should not be used as the right-hand side of assign- - ment statements). +
+ The getyx macro places the current cursor position of the given window + in the two integer variables y and x. --
- All of these interfaces are macros. A "&" is not neces- - sary before the variables 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 + beginning coordinates and size of the specified window. --
- 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 compatibility with older versions of curses. +
+ The return values of these macros are undefined (i.e., they should not + be used as the right-hand side of assignment statements). --
- curses(3x) +
+ 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. + 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 + 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 + implementations. The difference is hidden by means of the macro + getmaxyx. +
+ curses(3x), curs_legacy(3x), curs_opaque(3x) + curs_getyx(3x)-