Sets our main struct and passes it to the parent class
Get a pointer to the data of the image surface, for direct inspection or modification. A call to cairo_surface_flush() is required before accessing the pixel data to ensure that all pending drawing operations are finished. A call to cairo_surface_mark_dirty() is required after the data is modified. Since 1.2
Get the format of the surface. Since 1.2
Get the height of the image surface in pixels. Since 1.0
Get the main Gtk struct
Get the stride of the image surface in bytes Since 1.2
the main Gtk struct as a void*
Get the width of the image surface in pixels. Since 1.0
Writes the contents of surface to a new file filename as a PNG image. Since 1.0
Writes the image surface to the write function. Since 1.0
Creates an image surface of the specified format and dimensions. Initially the surface contents are all 0. (Specifically, within each pixel, each color or alpha channel belonging to format will be 0. The contents of bits within a pixel, but not belonging to the given format are undefined). Since 1.0
Creates an image surface for the provided pixel data. The output buffer must be kept around until the cairo_surface_t is destroyed or cairo_surface_finish() is called on the surface. The initial contents of data will be used as the initial image contents; you must explicitly clear the buffer, using, for example, cairo_rectangle() and cairo_fill() if you want it cleared. Note that the stride may be larger than width*bytes_per_pixel to provide proper alignment for each pixel and row. This alignment is required to allow high-performance rendering within cairo. The correct way to obtain a legal stride value is to call cairo_format_stride_for_width() with the desired format and maximum image width value, and then use the resulting stride value to allocate the data and to create the image surface. See cairo_format_stride_for_width() for example code. Since 1.0
Creates a new image surface and initializes the contents to the given PNG file. Since 1.0
Creates a new image surface from PNG data read incrementally via the read_func function. Since 1.0
This function provides a stride value that will respect all alignment requirements of the accelerated image-rendering code Since 1.6
the main Gtk struct
the main Gtk struct
Get the main Gtk struct
the main Gtk struct as a void*
Return mime data previously attached to surface using the specified mime type. If no data has been attached with the given mime type, data is set NULL. Since 1.10
Create a new surface that is as compatible as possible with an existing surface. For example the new surface will have the same fallback resolution and font options as other. Generally, the new surface will also use the same backend as other, unless that is not possible for some reason. The type of the returned surface may be examined with cairo_surface_get_type(). Initially the surface contents are all 0 (transparent if contents have transparency, black otherwise.) Use cairo_surface_create_similar_image() if you need an image surface which can be painted quickly to the target surface. Since 1.0
Create a new image surface that is as compatible as possible for uploading to and the use in conjunction with an existing surface. However, this surface can still be used like any normal image surface. Initially the surface contents are all 0 (transparent if contents have transparency, black otherwise.) Use cairo_surface_create_similar() if you don't need an image surface. Since 1.12
Create a new surface that is a rectangle within the target surface. All operations drawn to this surface are then clipped and translated onto the target surface. Nothing drawn via this sub-surface outside of its bounds is drawn onto the target surface, making this a useful method for passing constrained child surfaces to library routines that draw directly onto the parent surface, i.e. with no further backend allocations, double buffering or copies. Note The semantics of subsurfaces have not been finalized yet unless the rectangle is in full device units, is contained within the extents of the target surface, and the target or subsurface's device transforms are not changed. Since 1.10
Increases the reference count on surface by one. This prevents surface from being destroyed until a matching call to cairo_surface_destroy() is made. The number of references to a cairo_surface_t can be get using cairo_surface_get_reference_count(). Since 1.0
Decreases the reference count on surface by one. If the result is zero, then surface and all associated resources are freed. See cairo_surface_reference(). Since 1.0
Checks whether an error has previously occurred for this surface. Since 1.0
This function finishes the surface and drops all references to external resources. For example, for the Xlib backend it means that cairo will no longer access the drawable, which can be freed. After calling cairo_surface_finish() the only valid operations on a surface are getting and setting user, referencing and destroying, and flushing and finishing it. Further drawing to the surface will not affect the surface but will instead trigger a CAIRO_STATUS_SURFACE_FINISHED error. When the last call to cairo_surface_destroy() decreases the reference count to zero, cairo will call cairo_surface_finish() if it hasn't been called already, before freeing the resources associated with the surface. Since 1.0
Do any pending drawing for the surface and also restore any temporary modifications cairo has made to the surface's state. This function must be called before switching from drawing on the surface with cairo to drawing on it directly with native APIs. If the surface doesn't support direct access, then this function does nothing. Since 1.0
This function returns the device for a surface. See cairo_device_t. Since 1.10
Retrieves the default font rendering options for the surface. This allows display surfaces to report the correct subpixel order for rendering on them, print surfaces to disable hinting of metrics and so forth. The result can then be used with cairo_scaled_font_create(). Since 1.0
This function returns the content type of surface which indicates whether the surface contains color and/or alpha information. See cairo_content_t. Since 1.2
Tells cairo that drawing has been done to surface using means other than cairo, and that cairo should reread any cached areas. Note that you must call cairo_surface_flush() before doing such drawing. Since 1.0
Like cairo_surface_mark_dirty(), but drawing has been done only to the specified rectangle, so that cairo can retain cached contents for other parts of the surface. Any cached clip set on the surface will be reset by this function, to make sure that future cairo calls have the clip set that they expect. Since 1.0
Sets an offset that is added to the device coordinates determined by the CTM when drawing to surface. One use case for this function is when we want to create a cairo_surface_t that redirects drawing for a portion of an onscreen surface to an offscreen surface in a way that is completely invisible to the user of the cairo API. Setting a transformation via cairo_translate() isn't sufficient to do this, since functions like cairo_device_to_user() will expose the hidden offset. Note that the offset affects drawing to the surface as well as using the surface in a source pattern. Since 1.0
This function returns the previous device offset set by cairo_surface_set_device_offset(). Since 1.2
Set the horizontal and vertical resolution for image fallbacks. When certain operations aren't supported natively by a backend, cairo will fallback by rendering operations to an image and then overlaying that image onto the output. For backends that are natively vector-oriented, this function can be used to set the resolution used for these image fallbacks, (larger values will result in more detailed images, but also larger file sizes). Some examples of natively vector-oriented backends are the ps, pdf, and svg backends. For backends that are natively raster-oriented, image fallbacks are still possible, but they are always performed at the native device resolution. So this function has no effect on those backends. Note: The fallback resolution only takes effect at the time of completing a page (with cairo_show_page() or cairo_copy_page()) so there is currently no way to have more than one fallback resolution in effect on a single page. The default fallback resoultion is 300 pixels per inch in both dimensions. Since 1.2
This function returns the previous fallback resolution set by cairo_surface_set_fallback_resolution(), or default fallback resolution if never set. Since 1.8
This function returns the type of the backend used to create a surface. See cairo_surface_type_t for available types. Since 1.2
Returns the current reference count of surface. Since 1.4
Attach user data to surface. To remove user data from a surface, call this function with the key that was used to set it and NULL for data. Since 1.0
Return user data previously attached to surface using the specified key. If no user data has been attached with the given key this function returns NULL. Since 1.0
Emits the current page for backends that support multiple pages, but doesn't clear it, so that the contents of the current page will be retained for the next page. Use cairo_surface_show_page() if you want to get an empty page after the emission. There is a convenience function for this that takes a cairo_t, namely cairo_copy_page(). Since 1.6
Emits and clears the current page for backends that support multiple pages. Use cairo_surface_copy_page() if you don't want to clear the page. There is a convenience function for this that takes a cairo_t, namely cairo_show_page(). Since 1.6
Returns whether the surface supports sophisticated cairo_show_text_glyphs() operations. That is, whether it actually uses the provided text and cluster data to a cairo_show_text_glyphs() call. Note: Even if this function returns FALSE, a cairo_show_text_glyphs() operation targeted at surface will still succeed. It just will act like a cairo_show_glyphs() operation. Users can use this function to avoid computing UTF-8 text and cluster mapping if the target surface does not use it. Since 1.8
Attach an image in the format mime_type to surface. To remove the data from a surface, call this function with same mime type and NULL for data. The attached image (or filename) data can later be used by backends which support it (currently: PDF, PS, SVG and Win32 Printing surfaces) to emit this data instead of making a snapshot of the surface. This approach tends to be faster and requires less memory and disk space. The recognized MIME types are the following: CAIRO_MIME_TYPE_JPEG, CAIRO_MIME_TYPE_PNG, CAIRO_MIME_TYPE_JP2, CAIRO_MIME_TYPE_URI. See corresponding backend surface docs for details about which MIME types it can handle. Caution: the associated MIME data will be discarded if you draw on the surface afterwards. Use this function with care. Since 1.10
Return whether surface supports mime_type. Since 1.12
Returns an image surface that is the most efficient mechanism for modifying the backing store of the target surface. The region retrieved may be limited to the extents or NULL for the whole surface Note, the use of the original surface as a target or source whilst it is mapped is undefined. The result of mapping the surface multiple times is undefined. Calling cairo_surface_destroy() or cairo_surface_finish() on the resulting image surface results in undefined behavior. Since 1.12
Unmaps the image surface as returned from #cairo_surface_map_to_image(). The content of the image will be uploaded to the target surface. Afterwards, the image is destroyed. Using an image surface which wasn't returned by cairo_surface_map_to_image() results in undefined behavior. Since 1.12
Image surfaces provide the ability to render to memory buffers either allocated by cairo or by the calling code. The supported image formats are those defined in cairo_format_t.