table of contents
XEVI(3) | X FUNCTIONS | XEVI(3) |
NAME¶
XeviQueryExtension, XeviQueryVersion, XeviGetVisualInfo - X Extended Visual Information functionsSYNOPSIS¶
#include <X11/extensions/XEVI.h>int *major_version_return,
int *minor_version_return); int XeviGetVisualInfo (Display *dpy, VisualID *visual,
int n_visual, ExtendedVisualInfo ** evi_return,
int * n_info_return);
DESCRIPTION¶
The X11 Extended Visual Information extension (EVI) allows a client to determine information about core X visuals beyond what the core protocol provides.VisualID core_visual_id int screen int level unsigned int transparency_type unsigned int transparency_value unsigned int min_hw_colormaps unsigned int max_hw_colormaps unsigned int num_colormap_conflicts VisualID * colormap_conflictsThe combination of core_visual_id and screen number uniquely specify the visual being described. level returns the level number for the visual, 0 for normal planes, > 0 for overlays, < 0 for underlays. transparency_type returns the type of transparency supported by the visual. XEVI_TRANSPARENCY_NONE if there are no transparent pixels, XEVI_TRANSPARENCY_PIXEL if the visual supports a transparent pixel, XEVI_TRANSPARENCY_MASK if the visual supports transparent plane(s). transparency_value returns the pixel/plane value to set for transparency if transparency_type isn't XEVI_TRANSPARENCY_NONE. min_hw_colormaps and max_hw_colormaps return the minimum and maximum number of hardware colormaps backing up the visual. num_colormap_conflicts returns the number of elements in colormap_conflicts. This array returns a list of visuals that may cause conflicts in the use of the hardware colormap. For example, if a 12-bit hardware colormap is overloaded to support 8-bit colormaps, the corresponding 8-bit visuals would conflict with the 12-bit visuals.
ERRORS¶
XeviGetVisualInfo will return BadValue if passed an illegal visual ID, BadAccess if the X server does not respond, BadAlloc if there is a memory allocation failure.libXext 1.3.1 | X Version 11 |