X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_getyx.3x.html;h=689a1e6a64698ad10af3b338bb302944d55e7d01;hp=d6db1a8bc745af8e763802c46472a1fcc5bdee1b;hb=c6cfd97b8beaf0f6deafbf8aac7281cf6aa7f012;hpb=46722468f47c2b77b3987729b4bcf2321cccfd01 diff --git a/doc/html/man/curs_getyx.3x.html b/doc/html/man/curs_getyx.3x.html index d6db1a8b..689a1e6a 100644 --- a/doc/html/man/curs_getyx.3x.html +++ b/doc/html/man/curs_getyx.3x.html @@ -1,7 +1,6 @@ - +
+ +- +curs_getyx(3x) curs_getyx(3x) + + +-
+NAME
getyx, getparyx, getbegyx, getmaxyx - get curses cursor and window coordinates-SYNOPSIS
+SYNOPSIS
#include <curses.h> void getyx(WINDOW *win, int y, int x); @@ -58,7 +63,7 @@-DESCRIPTION
+DESCRIPTION
The getyx macro places the current cursor position of the given window in the two integer variables y and x. @@ -73,46 +78,61 @@-RETURN VALUE
- The return values of these macros are undefined (i.e., +RETURN VALUE
+ The return values of these macros are undefined (i.e., they should not be used as the right-hand side of assign- ment statements).-NOTES
+NOTES
All of these interfaces are macros. A "&" is not neces- sary before the variables y and x.-PORTABILITY
- The getyx, getparyx, getbegyx and getmaxyx functions are +PORTABILITY
+ The getyx, getparyx, getbegyx and getmaxyx macros 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. - - --SEE ALSO
- curses(3x) - - - + This implementation also provides functions getbegx, getb- + egy, getcurx, getcury, getmaxx, getmaxy, getparx and get- + pary 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). + 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. ++SEE ALSO
+ curses(3x), curs_legacy(3x), curs_opaque(3x) + curs_getyx(3x)-
- -Man(1) output converted with -man2html - +