begins an incremental load.
a gdkpixbuf.pixbuf_format.PixbufFormat holding information about the module.
returns whether a save option key is supported by the module
loads an image from a file.
loads an animation from a file.
continues an incremental load.
loads an image from data in memory.
the name of the module, usually the same as the usual file extension for images of this type, eg. "xpm", "jpeg" or "png".
the path from which the module is loaded.
the loaded gmodule.module_.Module.
saves a gdkpixbuf.pixbuf.Pixbuf to a file.
saves a gdkpixbuf.pixbuf.Pixbuf by calling the given gdkpixbuf.types.PixbufSaveFunc.
stops an incremental load.
A gdkpixbuf.pixbuf_module.PixbufModule contains the necessary functions to load and save images in a certain file format.
If gdkpixbuf.pixbuf.Pixbuf has been compiled with gmodule.module_.Module support, it can be extended by modules which can load (and perhaps also save) new image and animation formats.
Implementing modules
The gdkpixbuf.pixbuf.Pixbuf interfaces needed for implementing modules are contained in gdk-pixbuf-io.h (and gdk-pixbuf-animation.h if the module supports animations). They are not covered by the same stability guarantees as the regular GdkPixbuf API. To underline this fact, they are protected by the GDK_PIXBUF_ENABLE_BACKEND pre-processor symbol.
Each loadable module must contain a gdkpixbuf.types.PixbufModuleFillVtableFunc function named fill_vtable, which will get called when the module is loaded and must set the function pointers of the gdkpixbuf.pixbuf_module.PixbufModule.
In order to make format-checking work before actually loading the modules (which may require calling dlopen to load image libraries), modules export their signatures (and other information) via the fill_info function. An external utility, gdk-pixbuf-query-loaders, uses this to create a text file containing a list of all available loaders and their signatures. This file is then read at runtime by gdkpixbuf.pixbuf.Pixbuf to obtain the list of available loaders and their signatures.
Modules may only implement a subset of the functionality available via gdkpixbuf.pixbuf_module.PixbufModule. If a particular functionality is not implemented, the fill_vtable function will simply not set the corresponding function pointers of the gdkpixbuf.pixbuf_module.PixbufModule structure. If a module supports incremental loading (i.e. provides begin_load, stop_load and load_increment), it doesn't have to implement load, since gdkpixbuf.pixbuf.Pixbuf can supply a generic load implementation wrapping the incremental loading.
Installing modules
Installing a module is a two-step process: