X-Git-Url: http://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_kernel.3x.html;h=0df3eac0c17fcb340bd684976f662cf27092bc6d;hp=64a1ac83d6e25d274a971df59c257cb6e7592f50;hb=17c5992a16be94247b83f2bbb9accdd9b7e7bb72;hpb=6941ed1e8bfdfc7634a57655dc71e7a7ed02a6e8 diff --git a/doc/html/man/curs_kernel.3x.html b/doc/html/man/curs_kernel.3x.html index 64a1ac83..0df3eac0 100644 --- a/doc/html/man/curs_kernel.3x.html +++ b/doc/html/man/curs_kernel.3x.html @@ -1,6 +1,6 @@ @@ -94,15 +94,17 @@
- The getsyx routine returns the current coordinates of the virtual - screen cursor in y and x. If leaveok is currently TRUE, then -1,-1 is + The getsyx routine returns the current coordinates of the virtual + screen cursor in y and x. If leaveok is currently TRUE, then -1,-1 is returned. If lines have been removed from the top of the screen, using ripoffline, y and x include these lines; therefore, y and x should be used only as arguments for setsyx. + Few applications will use this feature, most use getyx instead. +
- The setsyx routine sets the virtual screen cursor to y, x. If y and x + The setsyx routine sets the virtual screen cursor to y, x. If y and x are both -1, then leaveok is set. The two routines getsyx and setsyx are designed to be used by a library routine, which manipulates curses windows but does not want to change the current position of the pro- @@ -110,6 +112,8 @@ do its manipulation of its own windows, do a wnoutrefresh on its win- dows, call setsyx, and then call doupdate. + Few applications will use this feature, most use wmove instead. +
The ripoffline routine provides access to the same facility that @@ -180,12 +184,13 @@
- The functions setsyx and getsyx are not described in the XSI Curses - standard, Issue 4. All other functions are as described in XSI Curses. + The virtual screen functions setsyx and getsyx are not described in the + XSI Curses standard, Issue 4. All other functions are as described in + XSI Curses. - The SVr4 documentation describes setsyx and getsyx as having return - type int. This is misleading, as they are macros with no documented se- - mantics for the return value. + The SVr4 documentation describes setsyx and getsyx as having return + type int. This is misleading, as they are macros with no documented + semantics for the return value.