You wrote on Fre, 25 Aug 2000:
Date: Fri, 25 Aug 2000 01:08:42 +0200
From: Sven Neumann [EMAIL PROTECTED]
[blurb about #ifdef GIMP_ENABLE_COMPAT_CRUFT]
Are you sure? Why does it work for the gimp-print plug-in then?
We've been using the old names. I ran Sven's conversion script
Hi,
Are you sure? Why does it work for the gimp-print plug-in then?
We've been using the old names. I ran Sven's conversion script to
generate the new names, and put a whole stack of #define's in the one
UI-related file that's shared between the 1.0 code and the 1.2 code.
It does
On Fri, Aug 25, 2000 at 10:03:43AM +0200, Sven Neumann [EMAIL PROTECTED]
wrote:
although not all that much so.
I was referring to the version of gimp-print that is included in gimp
CVS. It was left unchanged by me despite the inclusion of the line
#define GIMP_ENABLE_COMPAT_CRUFT in
Hi,
Maybe it's just gimp-perl then. Maybe it's the fact that gimp-perl simply
relies on all symbols, while gimp-print probably only relies on the most
common (small) subset. In that case, most probably only gimp-perl is hurt...
Which might also be the only plug-in where the community has
On Fri, Aug 25, 2000 at 06:02:30PM +0200, Sven Neumann [EMAIL PROTECTED]
wrote:
Maybe your problems to get gimp-perl going with GIMP_ENABLE_COMPAT_CRUFT
defined were related to the fact that gimp-perl seems to prefer to use
installed libgimp header files over the current ones in the source
While, in theory, I agree that having compatibility cruft inside a
software package is bad, I think breaking compatibility deep within a
feature freeze was a very bad idea.
I thought different this afternoon when I could just enable
GIMP_COMPAT_CRUFT_STH, but it just turned out that this define
Hi,
While, in theory, I agree that having compatibility cruft inside a
software package is bad, I think breaking compatibility deep within a
feature freeze was a very bad idea.
I thought different this afternoon when I could just enable
GIMP_COMPAT_CRUFT_STH, but it just turned out that
Date: Fri, 25 Aug 2000 01:08:42 +0200
From: Sven Neumann [EMAIL PROTECTED]
There were no API changes at all. All of the names that are standard
now have been around for a long time and the only thing we did was to
reverse the logic of the COMPAT_CRUFT defines. What was
