I have some experience with using glade/libglade to program UIs (gtk
builder should be the same or better), so I wanted to chime in even if
I'm a few days late on it.
On Sat, 2010-01-09 at 11:21 +0100, peter sikking wrote:
[...]
however,
let it be really clear that I will _not_ entertain the
It looks like this bug has already been reported, at
https://bugzilla.gnome.org/show_bug.cgi?id=605617
-- Bill
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
My way around this was to use a PF_DIRNAME immediately above the PF_STRING
and combining them for the total path.
Ah, thank you very much. I wasn't aware of PF_DIRNAME. It's missing in the
GIMP Python docs. This way I have a nice workaround which totally fits my
needs.
What else PF_ data types
I have a question about Gimp's lanczos3 image resizer.
I found that the results enlarged by Gimp lanczos3 resizer look very
different from other implementations' such as ImageMagick. I tried
implementing simple (no optimizations) lanczos3 resizer, it generates
the same results as ImageMagick.