X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_getyx.3x.html;h=f3bc2424463bc52b9718a2be8b2ecdf7918cf72d;hp=f5b379fe22fd5a0e9fbe673e5dea54ae8691c6a5;hb=9f479192e3ca3413d235c66bf058f8cc63764898;hpb=b0b1980be11bba618d84beb8b30ac94e2c820602 diff --git a/doc/html/man/curs_getyx.3x.html b/doc/html/man/curs_getyx.3x.html index f5b379fe..f3bc2424 100644 --- a/doc/html/man/curs_getyx.3x.html +++ b/doc/html/man/curs_getyx.3x.html @@ -1,7 +1,7 @@ - - + -curs_getyx 3x - + + +curs_getyx 3X + -

curs_getyx 3x

-
+

curs_getyx 3X

-
-curs_getyx(3x)                                           curs_getyx(3x)
+curs_getyx(3X)                                                  curs_getyx(3X)
 
 
 
 
-
-

NAME

-       getyx,  getparyx,  getbegyx,  getmaxyx - get curses cursor
-       and window coordinates
+

NAME

+       getyx,  getparyx,  getbegyx,  getmaxyx  -  get curses cursor and window
+       coordinates
 
 
-
-

SYNOPSIS

-       #include <curses.h>
+

SYNOPSIS

+       #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);
 
 
-
-

DESCRIPTION

-       The getyx macro places the current cursor position of  the
-       given window in the two integer variables y and x.
+

DESCRIPTION

+       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
+       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.
+       Like  getyx,  the  getbegyx  and  getmaxyx  macros  store  the  current
+       beginning coordinates and size of the specified window.
 
 
-
-

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).
+

RETURN VALUE

+       The return values of these macros are undefined (i.e., they should  not
+       be used as the right-hand side of assignment statements).
 
 
-
-

NOTES

-       All of these interfaces are macros.  A "&" is  not  neces-
-       sary before the variables y and x.
+

NOTES

+       All  of these interfaces are macros.  A "&" is not necessary before the
+       variables y and x.
 
 
-
-

PORTABILITY

-       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.
-
-       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.
+

PORTABILITY

+       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.
 
-
-

SEE ALSO

-       curses(3x), curs_legacy(3x), curs_opaque(3x)
+       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.
+
+
+

SEE ALSO

+       curses(3X), curs_legacy(3X), curs_opaque(3X)
 
 
 
-                                                         curs_getyx(3x)
+                                                                curs_getyx(3X)
-
-Man(1) output converted with man2html +
+ +