X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_getyx.3x.html;h=994e0f7f0abe5da2f67710192c8560d9b228d664;hp=cb7460b1aaedca6192b0b24984d7d46e6188acf2;hb=a90dd7b66fa711acd24d8181ea20e4f57d4b36cd;hpb=6208c89f98f1cf9fe0980bd8e791846ce007a13d diff --git a/doc/html/man/curs_getyx.3x.html b/doc/html/man/curs_getyx.3x.html index cb7460b1..994e0f7f 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 coordinates + getyx, getparyx, getbegyx, getmaxyx - get curses cursor and window + coordinates
@@ -60,52 +61,46 @@
- 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 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. + 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. - Like getyx, the getbegyx and getmaxyx macros store the - current beginning coordinates and size of the specified - window. + Like getyx, the getbegyx and getmaxyx macros store the current begin- + ning coordinates and size of the specified window.
- 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 return values of these macros are undefined (i.e., they should not + be used as the right-hand side of assignment statements).
- All of these interfaces are macros. A "&" is not neces- - sary 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 XSI Curses standard, Issue 4. + The getyx, getparyx, getbegyx and getmaxyx macros are described in the + XSI Curses standard, Issue 4. - This implementation also provides functions getbegx, getb- - egy, getcurx, getcury, getmaxx, getmaxy, getparx and get- - pary for compatibility with older versions of curses. + 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 imple- - mentations provide members of the WINDOW structure con- - taining 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). + 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 + direct use of its members). - Besides the problem of opaque structures, the data stored - in like-named members may not have like-values in differ- - ent 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. + 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.
@@ -113,7 +108,7 @@ - curs_getyx(3x) + curs_getyx(3x)