mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-11-18 09:00:34 +00:00
0b7418572e
Tue Jun 26 09:48:02 2001 Tim Janik <timj@gtk.org>
* Makefile.am (noinst_PROGRAMS): get rid of make-inline-pixbuf
* gdk-pixbuf-data.[hc]: provide gdk_pixbuf_new_from_stream()
instead from gdk_pixbuf_new_from_inline().
* gdk-pixdata.[hc]: auxillary GdkPixdata structure, public
installed API for applications that need to serialize/deserialize
on their own (gimp, BEAST).
* gdk-pixbuf/gdk-pixbuf-csource.c: provide publically installed
program that can dump images in CSource format and Pixbuf
stream format. supports RLE encoding, MACRO formatting etc...
invoke with --help.
Tue Jun 26 10:04:30 2001 Tim Janik <timj@gtk.org>
* gtk/gtkiconfactory.c:
* gtk/gtkitemfactory.c: use gdk_pixbuf_new_from_stream(). fixed up
item factory so inlined pixbufs actually work.
112 lines
2.4 KiB
Plaintext
112 lines
2.4 KiB
Plaintext
<!-- ##### SECTION Title ##### -->
|
|
Image Data in Memory
|
|
|
|
<!-- ##### SECTION Short_Description ##### -->
|
|
Creating a pixbuf from image data that is already in memory.
|
|
|
|
<!-- ##### SECTION Long_Description ##### -->
|
|
<para>
|
|
The most basic way to create a pixbuf is to wrap an existing pixel
|
|
buffer with a #GdkPixbuf structure. You can use the
|
|
gdk_pixbuf_new_from_data() function to do this You need to specify
|
|
the destroy notification function that will be called when the
|
|
data buffer needs to be freed; this will happen when a #GdkPixbuf
|
|
is finalized by the reference counting functions If you have a
|
|
chunk of static data compiled into your application, you can pass
|
|
in #NULL as the destroy notification function so that the data
|
|
will not be freed.
|
|
</para>
|
|
|
|
<para>
|
|
The gdk_pixbuf_new() function can be used as a convenience to
|
|
create a pixbuf with an empty buffer. This is equivalent to
|
|
allocating a data buffer using malloc() and then wrapping it with
|
|
gdk_pixbuf_new_from_data(). The gdk_pixbuf_new() function will
|
|
compute an optimal rowstride so that rendering can be performed
|
|
with an efficient algorithm.
|
|
</para>
|
|
|
|
<para>
|
|
As a special case, you can use the gdk_pixbuf_new_from_xpm_data()
|
|
function to create a pixbuf from inline XPM image data.
|
|
</para>
|
|
|
|
<para>
|
|
You can also copy an existing pixbuf with the gdk_pixbuf_copy()
|
|
function. This is not the same as just doing a gdk_pixbuf_ref()
|
|
on the old pixbuf; the copy function will actually duplicate the
|
|
pixel data in memory and create a new #GdkPixbuf structure for it.
|
|
</para>
|
|
|
|
<!-- ##### SECTION See_Also ##### -->
|
|
<para>
|
|
gdk_pixbuf_finalize().
|
|
</para>
|
|
|
|
<!-- ##### FUNCTION gdk_pixbuf_new ##### -->
|
|
<para>
|
|
|
|
</para>
|
|
|
|
@colorspace:
|
|
@has_alpha:
|
|
@bits_per_sample:
|
|
@width:
|
|
@height:
|
|
@Returns:
|
|
|
|
|
|
<!-- ##### FUNCTION gdk_pixbuf_new_from_data ##### -->
|
|
<para>
|
|
|
|
</para>
|
|
|
|
@data:
|
|
@colorspace:
|
|
@has_alpha:
|
|
@bits_per_sample:
|
|
@width:
|
|
@height:
|
|
@rowstride:
|
|
@destroy_fn:
|
|
@destroy_fn_data:
|
|
@Returns:
|
|
|
|
|
|
<!-- ##### FUNCTION gdk_pixbuf_new_from_xpm_data ##### -->
|
|
<para>
|
|
|
|
</para>
|
|
|
|
@data:
|
|
@Returns:
|
|
|
|
|
|
<!-- ##### FUNCTION gdk_pixbuf_new_subpixbuf ##### -->
|
|
<para>
|
|
|
|
</para>
|
|
|
|
@src_pixbuf:
|
|
@src_x:
|
|
@src_y:
|
|
@width:
|
|
@height:
|
|
@Returns:
|
|
|
|
|
|
<!-- ##### FUNCTION gdk_pixbuf_copy ##### -->
|
|
<para>
|
|
|
|
</para>
|
|
|
|
@pixbuf:
|
|
@Returns: <!--
|
|
Local variables:
|
|
mode: sgml
|
|
sgml-parent-document: ("../gdk-pixbuf.sgml" "book" "refsect2" "")
|
|
End:
|
|
-->
|
|
|
|
|