| gdk-pixbuf-file-saving {RGtk2} | R Documentation |
Saving a pixbuf to a file.
gdkPixbufSavev(object, filename, type, option.keys, option.values, .errwarn = TRUE)
gdkPixbufSave(object, filename, type, ..., .errwarn = TRUE)
gdkPixbufSaveToCallback(object, save.func, user.data, type, ..., .errwarn = TRUE)
gdkPixbufSaveToCallbackv(object, save.func, user.data, type, option.keys, option.values, .errwarn = TRUE)
gdkPixbufSaveToBuffer(object, type, ..., .errwarn = TRUE)
gdkPixbufSaveToBufferv(object, type, option.keys, option.values, .errwarn = TRUE)
These functions allow to save a GdkPixbuf in a number of
file formats. The formatted data can be written to a file
or to a memory buffer. gdk-pixbuf can also call a user-defined
callback on the data, which allows to e.g. write the image
to a socket or store it in a database.
GdkPixbufSaveFunc(buf, count, error, data)gdkPixbufSaveToCallback. It is called once for each block of
bytes that is "written" by gdkPixbufSaveToCallback. If
successful it should return TRUE. If an error occurs it should set
error and return FALSE, in which case gdkPixbufSaveToCallback
will fail with the same error.
Since 2.4
bufcountbuf.errorGError] A location to return an error.datagdkPixbufSaveToCallback.
Returns: [logical] TRUE if successful, FALSE (with error set) if failed.
Derived by RGtkGen from GTK+ documentation
http://developer.gnome.org/doc/API/2.0/gdk-pixbuf/gdk-pixbuf-file-saving.html