X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_color.3x.html;h=974a68f21e519642e8d3c17f259a0fea2aece841;hp=684605fe416cf5a746d73266a90d020806610f76;hb=77afe78361875f531dc2bf8d73f2e781c8e76176;hpb=027ae42953e3186daed8f3882da73de48291b606
diff --git a/doc/html/man/curs_color.3x.html b/doc/html/man/curs_color.3x.html
index 684605fe..974a68f2 100644
--- a/doc/html/man/curs_color.3x.html
+++ b/doc/html/man/curs_color.3x.html
@@ -1,7 +1,7 @@
@@ -109,43 +109,46 @@
background color number. For portable applications:
- The value of the first argument must be between 1 and
- COLOR_PAIRS-1.
+ COLOR_PAIRS-1, except that if default colors are used
+ (see use_default_colors) the upper limit is adjusted
+ to allow for extra pairs which use a default color in
+ foreground and/or background.
- - The value of the second and third arguments must be
- between 0 and COLORS. Color pair 0 is assumed to be
+ - The value of the second and third arguments must be
+ between 0 and COLORS. Color pair 0 is assumed to be
white on black, but is actually whatever the terminal
implements before color is initialized. It cannot be
modified by the application.
- If the color-pair was previously initialized, the screen
- is refreshed and all occurrences of that color-pair are
+ If the color-pair was previously initialized, the screen
+ is refreshed and all occurrences of that color-pair are
changed to the new definition.
- As an extension, ncurses allows you to set color pair 0
- via the assume_default_colors routine, or to specify the
- use of default colors (color number -1) if you first in-
+ As an extension, ncurses allows you to set color pair 0
+ via the assume_default_colors routine, or to specify the
+ use of default colors (color number -1) if you first in-
voke the use_default_colors routine.
- The init_color routine changes the definition of a color.
- It takes four arguments: the number of the color to be
- changed followed by three RGB values (for the amounts of
- red, green, and blue components). The value of the first
- argument must be between 0 and COLORS. (See the section
- Colors for the default color index.) Each of the last
- three arguments must be a value between 0 and 1000. When
- init_color is used, all occurrences of that color on the
+ The init_color routine changes the definition of a color.
+ It takes four arguments: the number of the color to be
+ changed followed by three RGB values (for the amounts of
+ red, green, and blue components). The value of the first
+ argument must be between 0 and COLORS. (See the section
+ Colors for the default color index.) Each of the last
+ three arguments must be a value between 0 and 1000. When
+ init_color is used, all occurrences of that color on the
screen immediately change to the new definition.
- The has_colors routine requires no arguments. It returns
- TRUE if the terminal can manipulate colors; otherwise, it
+ The has_colors routine requires no arguments. It returns
+ TRUE if the terminal can manipulate colors; otherwise, it
returns FALSE. This routine facilitates writing terminal-
- independent programs. For example, a programmer can use
- it to decide whether to use color or some other video at-
+ independent programs. For example, a programmer can use
+ it to decide whether to use color or some other video at-
tribute.
- The can_change_color routine requires no arguments. It
- returns TRUE if the terminal supports colors and can
- change their definitions; other, it returns FALSE. This
+ The can_change_color routine requires no arguments. It
+ returns TRUE if the terminal supports colors and can
+ change their definitions; other, it returns FALSE. This
routine facilitates writing terminal-independent programs.
The color_content routine gives programmers a way to find