| Revision
History |
@@ -323,7 +323,7 @@
6.3.2. wprintw()
and mvwprintw
- 6.3.3. vwprintw()
+ 6.3.3. vw_printw()
6.3.4. A Simple
printw example
@@ -355,7 +355,7 @@
7.2.2. wscanw() and
mvwscanw()
- 7.2.3. vwscanw()
+ 7.2.3. vw_scanw()
@@ -1539,7 +1539,7 @@ int main()
- These functions can be used interchangeably and it's a
+
These functions can be used interchangeably and it is a
matter of style as to which class is used. Let's see each one
in detail.
@@ -1679,7 +1679,7 @@ int main()
+ vw_printw()
This function is similar to vprintf(). This can be used when variable
@@ -1860,7 +1860,7 @@ int main()
+ vw_scanw()
This function is similar to vscanf(). This can be used when a variable
@@ -2224,8 +2224,8 @@ int main(int argc, char *argv[])
newwin(). It doesn't create any
thing on the screen actually. It allocates memory for a
structure to manipulate the window and updates the
- structure with data regarding the window like it's size,
- beginy, beginx etc.. Hence in curses, a window is just an
+ structure with data regarding the window such as its size,
+ beginy, beginx etc. Hence in curses, a window is just an
abstraction of an imaginary window, which can be
manipulated independent of other parts of screen. The
function newwin() returns a pointer to structure WINDOW,
@@ -2316,7 +2316,7 @@ WINDOW *create_newwin(int height, int width, int starty, int startx)
void destroy_win(WINDOW *local_win)
{
/* box(local_win, ' ', ' '); : This won't produce the desired
- * result of erasing the window. It will leave it's four corners
+ * result of erasing the window. It will leave its four corners
* and so an ugly remnant of window.
*/
wborder(local_win, ' ', ' ', ' ',' ',' ',' ',' ',' ');
@@ -2344,7 +2344,7 @@ void destroy_win(WINDOW *local_win)
- Don't scream. I know it's a big example. But I have to
+
Don't scream. I know it is a big example. But I have to
explain some important things here :-). This program
creates a rectangular window that can be moved with left,
right, up, down arrow keys. It repeatedly creates and
@@ -2711,7 +2711,7 @@ void print_in_middle(WINDOW *win, int starty, int startx, int width, char *strin
user. Let's deal with the keys first.
As you have seen in almost all of the above examples,
- it's very easy to get key input from the user. A simple way
+ it is very easy to get key input from the user. A simple way
of getting key presses is to use getch() function. The cbreak mode should be
enabled to read keys when you are interested in reading
@@ -2947,7 +2947,7 @@ void print_menu(WINDOW *menu_win, int highlight)
getmouse() returns the event into the pointer given to
- it. It's a structure which contains
+ it. It is a structure which contains
typedef struct
{
@@ -3188,7 +3188,7 @@ void report_choice(int mouse_x, int mouse_y, int *p_choice)
used to copy a window completely onto another window. It
takes the source and destination windows as parameters and
according to the rectangle specified, it copies the
- rectangular region from source to destination window. It's
+ rectangular region from source to destination window. Its
last parameter specifies whether to overwrite or just
overlay the contents on to the destination window. If this
argument is true, then the copying is non-destructive.
@@ -3668,7 +3668,7 @@ void print_in_middle(WINDOW *win, int starty, int startx, int width, char *strin
can be accessed using the function panel_userptr() which will return the user
pointer for the panel given as argument. After finding the
- next panel in the cycle It's brought to the top by the
+ next panel in the cycle It is brought to the top by the
function top_panel(). This function brings the panel given
as argument to the top of the panel stack.
@@ -3953,7 +3953,7 @@ void print_in_middle(WINDOW *win, int starty, int startx, int width, char *strin
the user presses <ENTER> present selection ends and
panel is resized by using the concept explained. While in
resizing mode the program doesn't show how the window is
- getting resized. It's left as an exercise to the reader to
+ getting resized. It is left as an exercise to the reader to
print a dotted border while it gets resized to a new
position.
@@ -5106,7 +5106,7 @@ int main()
This brings us to the interesting option for an item the
one and only O_SELECTABLE. We can turn it off by the
function item_opts_off() and after that that item is not
- selectable. It's like a grayed item in those fancy windows
+ selectable. It is like a grayed item in those fancy windows
menus. Let's put these concepts in practice with this
example
@@ -5206,10 +5206,10 @@ int main()
"MENUUSERPTR">17.9. The useful User Pointer
We can associate a user pointer with each item in the
- menu. It works the same way as user pointer in panels. It's
+ menu. It works the same way as user pointer in panels. It is
not touched by menu system. You can store any thing you
like in that. I usually use it to store the function to be
- executed when the menu option is chosen (It's selected and
+ executed when the menu option is chosen (It is selected and
may be the user pressed <ENTER>);
@@ -5318,7 +5318,7 @@ void func(char *name)
Well. If you have seen those forms on web pages which take
input from users and do various kinds of things, you might be
wondering how would any one create such forms in text mode
- display. It's quite difficult to write those nifty forms in
+ display. It is quite difficult to write those nifty forms in
plain ncurses. Forms library tries to provide a basic frame
work to build and maintain forms with ease. It has lot of
features(functions) which manage validation, dynamic
@@ -5989,7 +5989,7 @@ int set_field_status(FIELD *field, /* field to alter */
int field_status(FIELD *field); /* fetch status of field */
-
It's better to check the field's status only after
+
It is better to check the field's status only after
after leaving the field, as data buffer might not have
been updated yet as the validation is still due. To
guarantee that right status is returned, call
@@ -6042,7 +6042,7 @@ char *field_userptr(FIELD *field); /* fetch user pointer of the field */
field_opts_off(field_pointer, O_STATIC);
-
But it's usually not advisable to allow a field to
+
But it is usually not advisable to allow a field to
grow infinitely. You can set a maximum limit to the
growth of the field with
@@ -6342,7 +6342,7 @@ FIELDTYPE *field_type(FIELD *field); /* field to query */
The following are the pre-defined validation types. You
- can also specify custom validation, though it's a bit
+ can also specify custom validation, though it is a bit
tricky and cumbersome.