Enum cairo_status_t

cairo_status_t is used to indicate errors that can occur when using Cairo. In some cases it is returned directly by functions. but when using cairo_t, the last error, if any, is stored in the context and can be retrieved with cairo_status().

New entries may be added in future versions. Use cairo_status_to_string() to get a human-readable representation of an error message.

The enum base type is int .

Enum members

Name	Description
`CAIRO_STATUS_CLIP_NOT_REPRESENTABLE`	clip region not representable in desired format (Since 1.4)
`CAIRO_STATUS_DEVICE_ERROR`	an operation to the device caused an unspecified error (Since 1.10)
`CAIRO_STATUS_DEVICE_TYPE_MISMATCH`	the device type is not appropriate for the operation (Since 1.10)
`CAIRO_STATUS_FILE_NOT_FOUND`	file not found
`CAIRO_STATUS_FONT_TYPE_MISMATCH`	the font type is not appropriate for the operation (Since 1.8)
`CAIRO_STATUS_INVALID_CLUSTERS`	input clusters do not represent the accompanying text and glyph array (Since 1.8)
`CAIRO_STATUS_INVALID_CONTENT`	invalid value for an input `cairo_content_t`
`CAIRO_STATUS_INVALID_DASH`	invalid value for a dash setting
`CAIRO_STATUS_INVALID_DSC_COMMENT`	invalid value for a DSC comment (Since 1.2)
`CAIRO_STATUS_INVALID_FORMAT`	invalid value for an input `cairo_format_t`
`CAIRO_STATUS_INVALID_INDEX`	invalid index passed to getter (Since 1.4)
`CAIRO_STATUS_INVALID_MATRIX`	invalid matrix (not invertible)
`CAIRO_STATUS_INVALID_PATH_DATA`	input path data not valid
`CAIRO_STATUS_INVALID_POP_GROUP`	no saved group to pop, i.e. `cairo_pop_group`() without matching `cairo_push_group`()
`CAIRO_STATUS_INVALID_RESTORE`	`cairo_restore`() called without matching `cairo_save`()
`CAIRO_STATUS_INVALID_SIZE`	invalid value (typically too big) for the size of the input (surface, pattern, etc.) (Since 1.10)
`CAIRO_STATUS_INVALID_SLANT`	invalid value for an input `cairo_font_slant_t` (Since 1.8)
`CAIRO_STATUS_INVALID_STATUS`	invalid value for an input `cairo_status_t`
`CAIRO_STATUS_INVALID_STRIDE`	invalid value for stride (Since 1.6)
`CAIRO_STATUS_INVALID_STRING`	input string not valid UTF-8
`CAIRO_STATUS_INVALID_VISUAL`	invalid value for an input Visual*
`CAIRO_STATUS_INVALID_WEIGHT`	invalid value for an input `cairo_font_weight_t` (Since 1.8)
`CAIRO_STATUS_LAST_STATUS`	this is a special value indicating the number of status values defined in this enumeration. When using this value, note that the version of cairo at run-time may have additional status values defined than the value of this symbol at compile-time. (Since 1.10)
`CAIRO_STATUS_NEGATIVE_COUNT`	negative number used where it is not allowed (Since 1.8)
`CAIRO_STATUS_NO_CURRENT_POINT`	no current point defined
`CAIRO_STATUS_NO_MEMORY`	out of memory
`CAIRO_STATUS_NULL_POINTER`	null pointer
`CAIRO_STATUS_PATTERN_TYPE_MISMATCH`	the pattern type is not appropriate for the operation
`CAIRO_STATUS_READ_ERROR`	error while reading from input stream
`CAIRO_STATUS_SUCCESS`	no error has occurred
`CAIRO_STATUS_SURFACE_FINISHED`	target surface has been finished
`CAIRO_STATUS_SURFACE_TYPE_MISMATCH`	the surface type is not appropriate for the operation
`CAIRO_STATUS_TEMP_FILE_ERROR`	error creating or writing to a temporary file (Since 1.6)
`CAIRO_STATUS_USER_FONT_ERROR`	error occurred in a user-font callback function (Since 1.8)
`CAIRO_STATUS_USER_FONT_IMMUTABLE`	the user-font is immutable (Since 1.8)
`CAIRO_STATUS_USER_FONT_NOT_IMPLEMENTED`	user-font method not implemented (Since 1.10)
`CAIRO_STATUS_WRITE_ERROR`	error while writing to output stream

Authors

Johannes Pfau	cairoD
cairo team	cairo

Copyright

License

cairoD wrapper/bindings	Boost License 1.0
cairo	LGPL 2.1 / MPL 1.1