X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_getyx.3x.html;h=385eb8ed9588554a29a1075a966af10b997cb161;hp=c2b616d48c27e8a5648388f3a3e49573bac48a61;hb=81304798ee736c467839c779c9ca5dca48db7bea;hpb=cb4427a16794d98049b4d790b810d62217501f9f diff --git a/doc/html/man/curs_getyx.3x.html b/doc/html/man/curs_getyx.3x.html index c2b616d4..385eb8ed 100644 --- a/doc/html/man/curs_getyx.3x.html +++ b/doc/html/man/curs_getyx.3x.html @@ -1,6 +1,7 @@ - @@ -53,22 +54,22 @@

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

@@ -89,17 +90,18 @@
        getcury, getmaxx, getmaxy, getparx and getpary for  compatibility  with
        older versions of curses.
 
-       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
+       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  implementa-
-       tions.  The difference is hidden by means of the macro getmaxyx.
+       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