And now, the rest of the story. I've completed this project, and
everything worked out. Turns out that my perceived memory leak was
nothing more than normal growth of the undo stack; disable undos, and
the problem goes completely away. As for gimp_image_delete(), it occurs
as part of deleting
On Sun, Mar 11, 2012 at 8:12 PM, Tom Vrankar t...@cox.net wrote:
...[deleted]
The
only problems that remained were with the API. I guess there's a lot of
history there, but inconsistencies in it make it a chore to learn. And when
you call a function potentially thousands of times, you can't
On 12-03-11 08:12 PM, Tom Vrankar wrote:
only problems that remained were with the API. I guess there's a lot of
history there, but inconsistencies in it make it a chore to learn. And when
you call a function potentially thousands of times, you can't tolerate the
pointlessly repeating deprecated
On 02/16/2012 05:42 AM, Tom Vrankar wrote:
img =gp.gimp_image_new (1280, 720, 0)
dsp =gp.gimp_display_new (img)
lyr =gp.gimp_layer_new_from_drawable (src.layers[1], img)
img.insert_layer (lyr, position =0)
gp.gimp_display_delete (dsp)
If you eschew creating a new display for
