***************************************************************************
Copyright 2018-2023,2024 Thomas E. Dickey *
Copyright 1998-2016,2017 Free Software Foundation, Inc. *
*
Permission is hereby granted, free of charge, to any person obtaining a *
copy of this software and associated documentation files (the *
"Software"), to deal in the Software without restriction, including *
without limitation the rights to use, copy, modify, merge, publish, *
distribute, distribute with modifications, sublicense, and/or sell *
copies of the Software, and to permit persons to whom the Software is *
furnished to do so, subject to the following conditions: *
*
The above copyright notice and this permission notice shall be included *
in all copies or substantial portions of the Software. *
*
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS *
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF *
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. *
IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, *
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR *
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR *
THE USE OR OTHER DEALINGS IN THE SOFTWARE. *
*
Except as contained in this notice, the name(s) of the above copyright *
holders shall not be used in advertising or otherwise to promote the *
sale, use or other dealings in this Software without prior written *
authorization. *
***************************************************************************
$Id: curs_attr.3x,v 1.105 2024/04/27 17:54:42 tom Exp $
#include <curses.h>---------------------------------------------------------------------------int attr_get(attr_t *attrs, short *pair, void *opts); int wattr_get(WINDOW *win, attr_t *attrs, short *pair, void *opts); int attr_set(attr_t attrs, short pair, void *opts); int wattr_set(WINDOW *win, attr_t attrs, short pair, void *opts);
int attr_off(attr_t attrs, void *opts); int wattr_off(WINDOW *win, attr_t attrs, void *opts); int attr_on(attr_t attrs, void *opts); int wattr_on(WINDOW *win, attr_t attrs, void *opts);
int attroff(int attrs); int wattroff(WINDOW *win, int attrs); int attron(int attrs); int wattron(WINDOW *win, int attrs); int attrset(int attrs); int wattrset(WINDOW *win, int attrs);
int chgat(int n, attr_t attr, short pair, const void *opts); int wchgat(WINDOW *win, int n, attr_t attr, short pair, const void *opts); int mvchgat(int y, int x, int n, attr_t attr, short pair, const void *opts); int mvwchgat(WINDOW *win, int y, int x, int n, attr_t attr, short pair, const void *opts);
int color_set(short pair, void* opts); int wcolor_set(WINDOW *win, short pair, void* opts);
int standend(void); int wstandend(WINDOW *win); int standout(void); int wstandout(WINDOW *win);
These routines do not affect the attributes used
when erasing portions of the window.
See curs_bkgd(3X) for functions which modify the attributes used for
erasing and clearing.
---------------------------------------------------------------------------
The wattr_set function sets the current attributes of the given window to attrs, with color specified by pair.
Use wattr_get to retrieve attributes for the given window.
Use attr_on and wattr_on to turn on window attributes, i.e.,
values OR'd together in attr,
without affecting other attributes.
Use attr_off and wattr_off to turn off window attributes,
again values OR'd together in attr,
without affecting other attributes.
---------------------------------------------------------------------------
The int datatype used in the legacy routines is treated as if it is the same size as chtype (used by addch(3X)). It holds the common video attributes (such as bold, reverse), as well as a few bits for color. Those bits correspond to the A_COLOR symbol. The COLOR_PAIR macro provides a value which can be OR'd into the attribute parameter. For example, as long as that value fits into the A_COLOR mask, then these calls produce similar results:
.EX attrset(A_BOLD | COLOR_PAIR(pair)); attr_set(A_BOLD, pair, NULL);
However, if the value does not fit, then the COLOR_PAIR macro uses only the bits that fit. For example, because in \%ncurses A_COLOR has eight (8) bits, then COLOR_PAIR(259) is 4 (i.e., 259 is 4 more than the limit 255).
The PAIR_NUMBER macro extracts a pair number from an int (or chtype). For example, the input and output values in these statements would be the same:
.EX int value = A_BOLD | COLOR_PAIR(input); int output = PAIR_NUMBER(value);
The attrset routine is a legacy feature predating SVr4 curses but kept in X/Open Curses for the same reason that SVr4 curses kept it: compatibility.
The remaining attr* functions operate exactly like the corresponding attr_* functions, except that they take arguments of type int rather than attr_t.
There is no corresponding \%attrget function as such
in X/Open Curses,
although \%ncurses provides \%getattrs
(see \%curs_legacy(3X)).
---------------------------------------------------------------------------
In these functions,
the color pair argument is a color pair index
(as in the first argument of init_pair, see curs_color(3X)).
---------------------------------------------------------------------------
X/Open Curses does not mark these \*(``restricted\*('', because
.bP
they have well established legacy use, and
.bP
there is no ambiguity about the way the attributes
might be combined with a color pair.
---------------------------------------------------------------------------
Name Description |
A_NORMAL Normal display (no highlight) |
A_STANDOUT |
Best highlighting mode of the terminal |
A_UNDERLINE Underlining |
A_REVERSE Reverse video |
A_BLINK Blinking |
A_DIM Half bright |
A_BOLD Extra bright or bold |
A_PROTECT Protected mode |
A_INVIS Invisible or blank mode |
A_ALTCHARSET Alternate character set |
A_ITALIC Italics (non-X/Open extension) |
A_CHARTEXT Bit-mask to extract a character |
A_COLOR |
Bit-mask to extract a color (legacy routines) |
These video attributes are supported by attr_on and related functions (which also support the attributes recognized by attron, etc.):
Name Description |
WA_HORIZONTAL Horizontal highlight |
WA_LEFT Left highlight |
WA_LOW Low highlight |
WA_RIGHT Right highlight |
WA_TOP Top highlight |
WA_VERTICAL Vertical highlight |
The return values of many of these routines are not meaningful (they are
implemented as macro-expanded assignments and simply return their argument).
The SVr4 manual page claims (falsely) that these routines always return 1.
---------------------------------------------------------------------------
X/Open Curses does not specify any error conditions.
This implementation .bP returns an error if the window pointer is null. .bP returns an error if the color pair parameter for wcolor_set is outside the range 0..COLOR_PAIRS-1. .bP does not return an error if either of the parameters of wattr_get used for retrieving attribute or color pair values is NULL.
Functions prefixed with \*(``mv\*('' first perform cursor movement and
fail if the position
( y , x ) is outside the window boundaries.
---------------------------------------------------------------------------
attroff, wattroff, attron, wattron, attrset, wattrset, standend and standout.
Color pair values can only be OR'd with attributes if the pair
number is less than 256.
The alternate functions such as color_set can pass a color pair
value directly.
However, \%ncurses ABI 4 and 5 simply OR this value
within the alternate functions.
You must use \%ncurses ABI 6 to support more than 256 color pairs.
---------------------------------------------------------------------------
Each of the functions added by XSI Curses has a parameter opts,
which X/Open Curses still (after more than twenty years) documents
as reserved for future use, saying that it should be NULL.
This implementation uses that parameter in ABI 6 for the functions which
have a color pair parameter to support extended color pairs:
.bP
For functions which modify the color, e.g.,
wattr_set and wattr_on,
if opts is set it is treated as a pointer to int,
and used to set the color pair instead of the short pair parameter.
.bP
For functions which retrieve the color, e.g.,
wattr_get,
if opts is set it is treated as a pointer to int,
and used to retrieve the color pair as an int value,
in addition to
retrieving it via the standard pointer to short parameter.
.bP
For functions which turn attributes off, e.g.,
wattr_off,
the opts parameter is ignored except
except to check that it is NULL.
---------------------------------------------------------------------------
Very old versions of this library did not force an update of the screen when changing the attributes. Use touchwin to force the screen to match the updated attributes.
X/Open Curses states that whether the traditional functions attron/attroff/attrset can manipulate attributes other than A_BLINK, A_BOLD, A_DIM, A_REVERSE, A_STANDOUT, or A_UNDERLINE is \*(``unspecified\*(''. Under this implementation as well as SVr4 curses, these functions correctly manipulate all other highlights (specifically, A_ALTCHARSET, A_PROTECT, and A_INVIS).
X/Open Curses added these entry points:
attr_get, attr_on, attr_off, attr_set, wattr_on, wattr_off, wattr_get, wattr_set
The new functions are intended to work with a new series of highlight macros prefixed with WA_. The older macros have direct counterparts in the newer set of names:
Name Description |
WA_NORMAL Normal display (no highlight) |
WA_STANDOUT |
Best highlighting mode of the terminal |
WA_UNDERLINE Underlining |
WA_REVERSE Reverse video |
WA_BLINK Blinking |
WA_DIM Half bright |
WA_BOLD Extra bright or bold |
WA_ALTCHARSET Alternate character set |
X/Open Curses does not assign values to these symbols, nor does it state whether or not they are related to the similarly-named A_NORMAL, etc.: .bP X/Open Curses specifies that each pair of corresponding A_ and WA_-using functions operates on the same current-highlight information. .bP However, in some implementations, those symbols have unrelated values.
For example, the Solaris xpg4 (X/Open) curses declares attr_t to be an unsigned short integer (16-bits), while chtype is a unsigned integer (32-bits). The WA_ symbols in this case are different from the A_ symbols because they are used for a smaller datatype which does not represent A_CHARTEXT or A_COLOR. In this implementation (as in many others), the values happen to be the same because it simplifies copying information between chtype and cchar_t variables. .bP Because \%ncurses's attr_t can hold a color pair (in the A_COLOR field), a call to wattr_on, wattr_off, or wattr_set may alter the window's color. If the color pair information in the attribute parameter is zero, no change is made to the window's color. This is consistent with SVr4 curses; X/Open Curses does not specify this.
The X/Open Curses extended conformance level adds new highlights
A_HORIZONTAL, A_LEFT, A_LOW, A_RIGHT, A_TOP,
A_VERTICAL (and corresponding WA_ macros for each).
As of August 2013,
no known terminal provides these highlights
(i.e., via the sgr1 capability).
---------------------------------------------------------------------------
As seen in 2.8BSD, curses assumed 7-bit characters, using the eighth bit of a byte to represent the standout feature (often implemented as bold and/or reverse video). The BSD curses library provided functions standout and standend which were carried along into X/Open Curses due to their pervasive use in legacy applications.
Some terminals in the 1980s could support a variety of video attributes, although the BSD curses library could do nothing with those. System V (1983) provided an improved curses library. It defined the A_ symbols for use by applications to manipulate the other attributes. There are few useful references for the chronology.
Goodheart's book UNIX Curses Explained (1991) describes SVr3 (1987), commenting on several functions: .bP the attron, attroff, attrset functions (and most of the functions found in SVr4 but not in BSD curses) were introduced by System V, .bP the alternate character set feature with A_ALTCHARSET was added in SVr2 and improved in SVr3 (by adding acs_map[]), .bP start_color and related color-functions were introduced by System V.3.2, .bP pads, soft-keys were added in SVr3, and
Goodheart did not mention the background character or the cchar_t type. Those are respectively SVr4 and X/Open features. He did mention the A_ constants, but did not indicate their values. Those were not the same in different systems, even for those marked as System V.
Different Unix systems used different sizes for the bit-fields in chtype for characters and colors, and took into account the different integer sizes (32-bit versus 64-bit).
This table showing the number of bits for A_COLOR and A_CHARTEXT was gleaned from the curses header files for various operating systems and architectures. The inferred architecture and notes reflect the format and size of the defined constants as well as clues such as the alternate character set implementation. A 32-bit library can be used on a 64-bit system, but not necessarily the reverse.
Bits \& |
Year System Arch Color Char Notes |
1992 Solaris 5.2 32 6 17 SVr4 curses |
1992 HP-UX 9 32 no 8 SVr2 curses |
1992 AIX 3.2 32 no 23 SVr2 curses |
1994 OSF/1 r3 32 no 23 SVr2 curses |
1995 HP-UX 10.00 32 6 16 SVr3 curses_colr |
1995 HP-UX 10.00 32 6 8 SVr4, X/Open curses |
1995 Solaris 5.4 32/64 7 16 X/Open curses |
1996 AIX 4.2 32 7 16 X/Open curses |
1996 OSF/1 r4 32 6 16 X/Open curses |
1997 HP-UX 11.00 32 6 8 X/Open curses |
2000 U/Win 32/64 7/31 16 uses chtype |
Notes:
Regarding HP-UX, .bP HP-UX 10.20 (1996) added support for 64-bit PA-RISC processors in 1996. .bP HP-UX 10.30 (1997) marked \*(``curses_colr\*('' obsolete. That version of curses was dropped with HP-UX 11.30 in 2006.
Regarding OSF/1 (and Tru64), .bP These used 64-bit hardware. Like \%ncurses, the OSF/1 curses interface is not customized for 32-bit and 64-bit versions. .bP Unlike other systems which evolved from AT&T code, OSF/1 provided a new implementation for X/Open curses.
Regarding Solaris, .bP The initial release of Solaris was in 1992. .bP The xpg4 (X/Open) curses was developed by MKS from 1990 to 1995. Sun's copyright began in 1996. .bP Sun updated the X/Open curses interface after 64-bit support was introduced in 1997, but did not modify the SVr4 curses interface.
Regarding U/Win, .bP Development of the curses library began in 1991, stopped in 2000. .bP Color support was added in 1998. .bP The library uses only chtype (no cchar_t).
Once X/Open curses was adopted in the mid-1990s, the constraint of a 32-bit interface with many colors and wide-characters for chtype became a moot point. The cchar_t structure (whose size and members are not specified in X/Open Curses) could be extended as needed.
Other interfaces are rarely used now: .bP BSD curses was improved slightly in 1993/1994 using Keith Bostic's modification to make the library 8-bit clean for nvi(1). He moved standout attribute to a structure member.
The resulting 4.4BSD curses was replaced by \%ncurses over the next ten years. .bP U/Win is rarely used now. ---------------------------------------------------------------------------