X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_getyx.3x.html;h=7543eb2f6f30afca25b2d316c21ac5a98810efe8;hp=7f098479241199faacc310053affb7bf2063ea5a;hb=a6eb34d7fec8170a8715f9e53ca2f96452dd30dd;hpb=5925150381bb42a4d8c7116d62c348a7b84309f3 diff --git a/doc/html/man/curs_getyx.3x.html b/doc/html/man/curs_getyx.3x.html index 7f098479..7543eb2f 100644 --- a/doc/html/man/curs_getyx.3x.html +++ b/doc/html/man/curs_getyx.3x.html @@ -64,12 +64,12 @@ 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

@@ -90,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