gtk2/modules/engines/pixbuf
Nicola Fontana 1e1131c959 Do not use static GTypeInfo and GInterfaceInfo
Either g_type_register_static_simple (used by G_DEFINE_TYPE_EXTENDED)
and G_IMPLEMENT_INTERFACE use automatic variables for GTypeInfo and
GInterfaceInfo structs, while tutorials and source code often use
static variables. This commit consistently adopts the former method.

https://bugzilla.gnome.org/show_bug.cgi?id=600158
2009-11-06 01:21:09 +01:00
..
ChangeLog Update README files to refer to git 2009-03-31 18:49:48 -04:00
Makefile.am Add git.mk to generate .gitignore files 2009-05-04 14:29:21 -04:00
pixbuf-draw.c Do not use static GTypeInfo and GInterfaceInfo 2009-11-06 01:21:09 +01:00
pixbuf-main.c modules/engines/ms-windows/msw_rc_style.c 2004-11-19 23:30:47 +00:00
pixbuf-rc-style.c Do not use static GTypeInfo and GInterfaceInfo 2009-11-06 01:21:09 +01:00
pixbuf-rc-style.h modules/engines/pixbuf/pixbuf-style.h include <gtk/gtk.h> instead of 2008-05-27 23:45:36 +00:00
pixbuf-render.c Remove unnecessary NULL checks before g_free(). (#369666, Morten Welinder, 2007-03-09 21:57:37 +00:00
pixbuf-style.h modules/engines/pixbuf/pixbuf-style.h include <gtk/gtk.h> instead of 2008-05-27 23:45:36 +00:00
pixbuf.h Move G_GNUC_INTERNAL before function declarations. (#352276, Damien 2006-12-23 03:35:21 +00:00
README Initial revision 2000-02-07 02:36:39 +00:00

The code in this directory is a GTK+ theme engine based on the earlier
pixmap theme engine.

The config files are meant to be compatible, but instead of rendering
using Imlib, it renders using GdkPixbuf.  This makes the memory
management much more understandable, and also allows us to use
GdkPixbuf's high quality scaling.

Most of the code was reworked/rewritten in the process to make it more
understandable and maintainable.

There are lots of bugs here, a considersable number of bugs. But it's
cleaned up a great deal from the older pixmap engine. Please don't
make it uglier again.

Owen Taylor <otaylor@redhat.com>
6 February 2000