Hi David -

Thanks for your reply.  Yes, gimp-image-delete is what I needed.  Several
other folks have also responded with the same answer.  The reason that I
overlooked this is that I failed to associate "deleting" an image (which I
think of as deleting the permanent file on disk) with closing the image.  I
wasn't talking about closing the display.  In fact, since I'm working on
batch mode scripts, a display will not be involved at all.  I just need to
close an image to free its associated memory after I'm done processing that
image and ready to move on to another one.

What am I up to?  Working at digital archiving images of well logs for the
oil and gas industry.  Up to a foot wide by several hundred feet in length.
Far too many and far too time consuming to work with all of them manually,
therefore need to use batch mode.  Require custom scripts and plug-ins to
perform several image cleanup steps that aren't included among the
capabilities that get installed with the gimp.  Must deal with varying
brightness and contrast, smudges, stains, and reproduction anomalies, both
between different images, AND within a single image.  Also, must reduce
color levels to facilitate image compression, while maintaining all
significant image details as closely as possible.  Not an easy thing to do,
even when each log image is tackled manually by an experienced user.  I have
developed plug-ins to perform the specific types of image cleanup that I
need.  Now I'm working on scripts to combine those along with other supplied
gimp capabilities to perform the complete set of tasks that are needed for
each image.

The scripts that I'm coming up with are very simple and basic, it's the
plug-ins that do the really tricky stuff.  The only problems that I have
right now are the following two issues:

1. I can't figure out anyway to pass a string argument (which requires
double quotes) from the command line under Windows.  Something drops or
otherwise mangles the quotes along the way, and I'm pretty certain that the
command shell interpreter is NOT responsible for them getting dropped.  I'm
considering some possibilities for working around this problem, but they are
really ugly...

2. I seem to be running into some kind of size limit, and I'm very worried
that it may be exactly the same maximum image size that is supported by
ImageMagick.  That limit is defined by 2GB max addressable space for a user
program under Windows, divided by 5 bytes per pixel (R, G, B, alpha, index).
Whether or not it is really the same problem, I am definitely running into
some kind of a bug or limitation somewhere just a little over 400 mega
pixels with my grayscale images.


----- Original Message -----
From: "David Hodson" <[EMAIL PROTECTED]>
To: "Kevin Myers" <[EMAIL PROTECTED]>
Sent: Sunday, October 20, 2002 8:48 AM
Subject: Re: [Gimp-user] Close Image from Script

> Kevin Myers wrote:
> > How can a script-fu script close an open image?  I've searched all
> > the PDB and can't seem to find a way.  I can load images, save images,
> > create new images, and list open images, but I can't find any way to
> > an open image!  What am I missing???  Thanks.
> Delete the image, or close the display? Don't know about script-fu, but
> using the procedural interface from C, they're different things. An
> image may (or may not) have one or more displays. Displays can be opened
>   (on a particular image) and closed, and an image can be deleted when
> all its displays are closed. (IIRC).
> (Hmm... ultra large images? Batch processing? What are you up to?)
> --
> David Hodson  --  this night wounds time

Gimp-user mailing list

Reply via email to