X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_getyx.3x.html;h=cb7460b1aaedca6192b0b24984d7d46e6188acf2;hp=796528f82b777489eb3f0a7d67f60ea45f0689b8;hb=5461fc336d03fbfea6b85ac21c6d49c528f6752d;hpb=027ae42953e3186daed8f3882da73de48291b606 diff --git a/doc/html/man/curs_getyx.3x.html b/doc/html/man/curs_getyx.3x.html index 796528f8..cb7460b1 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) --
+
getyx, getparyx, getbegyx, getmaxyx - get curses cursor and window coordinates --
+
#include <curses.h> void getyx(WINDOW *win, int y, int x); @@ -61,8 +59,7 @@ 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. @@ -76,44 +73,58 @@ 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). --
+
All of these interfaces are macros. A "&" is not neces- sary 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 getbegx, getbegy, - getcurx, getcury, getmaxx, getmaxy, getparx and getpary - for compatibility with older versions of curses. X/Open - does not define a corresponding getcuryx function, though - that would be needed to make references to the WINDOW - structure opaque. + 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). --
- curses(3x) + 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. + + +
+ curses(3x), curs_legacy(3x), curs_opaque(3x) curs_getyx(3x)-