X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_kernel.3x.html;h=4238ed8cb38a776246fba11ee5cbeabc6757cca7;hp=a7303ec549c82e9b7ac081bf01fd567964d01df8;hb=d97989d1e0db7282c723cabb44b991b951790006;hpb=ed646e3f683083e787c6ba773364401dc9fa9d40 diff --git a/doc/html/man/curs_kernel.3x.html b/doc/html/man/curs_kernel.3x.html index a7303ec5..4238ed8c 100644 --- a/doc/html/man/curs_kernel.3x.html +++ b/doc/html/man/curs_kernel.3x.html @@ -1,6 +1,6 @@
- +- 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.