|
|
#include <curses.h>int getn_wstr(wchar_t *wstr, int n);
int get_wstr(wchar_t *wstr);
int mvgetn_wstr(int y, int x, wchar_t *wstr, int n);
int mvget_wstr(int y, int x, wchar_t *wstr);
int mvwgetn_wstr(WINDOW *win, int y, int x, wchar_t *wstr, int n);
int mvwget_wstr(WINDOW *win, int y, int x, wchar_t *wstr);
int wgetn_wstr(WINDOW *win, wchar_t *wstr, int n);
int wget_wstr(WINDOW *win, wchar_t *wstr);
The user's erase and kill characters are interpreted and affect the sequence of characters returned.
The effect of wget_wstr(3curses) is as though a series of calls to wget_wch(3curses) were made.
The effect of mvget_wstr(3curses) is as though a call to move(3curses) and then a series of calls to get_wch(3curses) were made.
The effect of mvwget_wstr(3curses) is as though a call to wmove(3curses) and then a series of calls to wget_wch(3curses) were made.
The effect of mvgetn_wstr(3curses) is as though a call to move(3curses) and then a series of calls to get_wch(3curses) were made.
The effect of mvwgetn_wstr(3curses) is as though a call to wmove(3curses) and then a series of calls to wget_wch(3curses) were made.
The getn_wstr(3curses), mvgetn_wstr(3curses), mvwgetn_wstr(3curses) and wgetn_wstr(3curses) functions read at most n characters, letting the application prevent overflow of the input buffer.
These functions cannot return KEY_ values as there is no way to distinguish a KEY_ value from a valid wchar_t value.