Am Montag, den 18.06.2007, 19:08 -0600 schrieb Elijah Newren:
> On 6/18/07, Hubert Figuiere <[EMAIL PROTECTED]> wrote:
> >
> > I don't agree with that one. It is much simplier to add a C++ compile
> > test. Afterall, which platform does not have a C++ compiler? Why
> > reinventing the wheel yet aga
Torsten Schoenfeld wrote:
> On Mon, 2007-06-18 at 09:55 -0300, Johan Dahlin wrote:
>
void (* set_property)(GtkBuildable *buildable,
GtkBuilder*builder,
const gchar *name,
CC'd the -devel list as I think this is relevant there..
On Tue, 2007-06-19 at 11:56 +1000, Daniel Kasak wrote:
> On Thu, 2007-06-14 at 21:54 +0200, [EMAIL PROTECTED] wrote:
[snip]
> > The data model often changes drastically, a lot of rows and
> > subtrees are modified, deleted, created, et
In light of bug 438456, is there (or should there be) a way to
blacklist a certain
theme engine for a certain version range?
Bug 438456 causes memory corruption in any gtk+ application it is applied to.
Morten
___
gtk-devel-list mailing list
gtk-devel-l
GTK+ 2.11.4 is now available for download at:
ftp://ftp.gtk.org/pub/gtk/2.11/
http://ftp.gnome.org/pub/GNOME/sources/gtk+/2.11/
gtk+-2.11.4.tar.bz2 md5sum: a3baab72d34b6fa9c01578f1f2dd84f0
gtk+-2.11.4.tar.gzmd5sum: b43f01b91ff406b2cd8d009eff03a2cc
This is another development release lead
On 6/19/07, Morten Welinder <[EMAIL PROTECTED]> wrote:
> In light of bug 438456, is there (or should there be) a way to
> blacklist a certain
> theme engine for a certain version range?
>
> Bug 438456 causes memory corruption in any gtk+ application it is applied to.
>
I don't see how this is diff
> I don't see how this is different from any other memory corrupting bug
> in, say, a library.
>From a technical standpoint it is not.
However, a theme is a library that is loaded into your application by
the end-user.
Even if he is not particularly aware of doing so.
The application programmer
