> Hi there, > > the GIMP Script-Fu engine doesn't make a difference between registered > definitions and local ones. > This could be a problem, because if I write a script with a local > function, but another script has that function too, GIMP could use the > other function. With many scripts in the scripts folder it's hard to > find out, which script causes the problem.
This is right; however, I think it is better to educate ourselves only to define local functions in local scope, i.e. within a define form, which is perfectly feasonable. Functions local to a script should be truly local, but please consider the case of library functions. > It would be nice if GIMP could prefer local definitions to global ones > or if just registered definitions would go global. > > > Thx, > Samuel > > > ------------------------------ > > Message: 2 > Date: Fri, 19 Sep 2008 19:41:14 +0200 > From: Sven Neumann <[EMAIL PROTECTED]> > Subject: Re: [Gimp-developer] some minor nits > To: peter sikking <[EMAIL PROTECTED]> > Cc: gimp-developer List <gimp-developer@lists.XCF.Berkeley.EDU> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain > > Hi, > > On Fri, 2008-09-19 at 12:46 +0200, peter sikking wrote: > >> the structure is good: 'New...' _must_ remain a first level menu item, >> the rest is OK to have in a sub-menu. >> >> My solution is to rename the 'New' sub-menu to 'Create' > > We have done that change in trunk. > > > Sven > > > > > ------------------------------ > > _______________________________________________ > Gimp-developer mailing list > Gimp-developer@lists.XCF.Berkeley.EDU > https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer > > > End of Gimp-developer Digest, Vol 72, Issue 15 > ********************************************** > _______________________________________________ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
