cursscanw(3X)                                                  cursscanw(3X)



NAME
       scanw, wscanw, mvscanw, mvwscanw, vwscanw, vwscanw - convert formatted
       input from a curses window

SYNOPSIS
       ##include <>

       int scanw(char **fmt,, ...);;
       int wscanw(WINDOW **win,, char **fmt,, ...);;
       int mvscanw(int y,, int x,, char **fmt,, ...);;
       int mvwscanw(WINDOW **win,, int y,, int x,, char **fmt,, ...);;
       int vwscanw(WINDOW **win,, char **fmt,, valist varglist);;
       int vwscanw(WINDOW **win,, char **fmt,, valist varglist);;

DESCRIPTION
       The scanw, wscanw and mvscanw routines  are  analogous  to  scanf  [see
       scanf(3S)].   The  effect  of  these routines is as though wgetstr were
       called on the  window,  and  the  resulting  line  used  as  input  for
       sscanf(3).   Fields which do not map to a variable in the fmt field are
       lost.

       The vwscanw and vwscanw routines are analogous to vscanf.   They  per-
       form  a wscanw using a variable argument list.  The third argument is a
       valist, a pointer to a list of arguments, as defined in <>.

RETURN VALUE
       vwscanw returns ER on failure and an integer equal to  the  number  of
       fields scanned on success.

       Applications  may  use the return value from the scanw, wscanw, mvscanw
       and mvwscanw routines to determine the  number  of  fields  which  were
       mapped in the call.

PORTABILITY
       The  XSI Curses standard, Issue 4 describes these functions.  The func-
       tion vwscanw is marked TO BE WITHDRAWN, and is  to  be  replaced  by  a
       function  vwscanw  using  the  <>  interface.  The Single Unix
       Specification, Version 2 states that vwscanw  is preferred to  vwscanw
       since  the  latter requires including <>, which cannot be used
       in the same file as <>.  This  implementation  uses  <>
       for both, because that header is included in <.

       Both  XSI and The Single Unix Specification, Version 2 state that these
       functions return ER or OK.  Since the underlying scanf can return  the
       number  of  items scanned, and the SVr4 code was documented to use this
       feature, this is probably an editing error which was introduced in XSI,
       rather  than  being  done  intentionally.  Portable applications should
       only test if the return value is ER, since  the  OK  value  (zero)  is
       likely  to be misleading.  One possible way to get useful results would
       be to use a "%n" conversion at the end of the format string  to  ensure
       that something was processed.

SEE ALSO
       curses(3X), cursgetstr(3X), cursprintw(3X), scanf(3S)



                                                                cursscanw(3X)