The method of calling it that I mentioned always worked fine with the GIMP 2.2. It was only after the upgrade to 2.6 that it started spawning the extra process and leaving it behind, and I'm not sure what the difference is. So I will look into using the script-fu server solution in the future after I can work out all the how's and so-forth, but for now if anyone knows the inner workings of gimp-quit or why calling gimp.exe from the command line forks two gimp processes I'd sure be grateful for some insight. Thanks.
2011/2/26 Aurimas JuÅka <aurimas.juska@xxxxxxxxx>
Hi,
For what you want to do, Script-fu server should be the best option.
On Sun, Feb 27, 2011 at 12:15 AM, Roger Penn <roger.penn@xxxxxxxxx> wrote:
> I'm using the GIMP to create custom graphics on the fly for a CMS by calling
> the script from the web page through ASP.NET.
See http://docs.gimp.org/en/gimp-filters-script-fu.html (Section
10.6.4. Start Server).
_______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer