dd's scripts running in Gimp-2.7.3

Rod · **Joined:** May 16, 2010 **Posts:** 14715 **Location:** USA

Has anyone been able to get them to work.
http://registry.gimp.org/files/rendertexture1_3.py.txt

and

http://registry.gimp.org/files/bevel1_53.py.txt

I can not get either to even show in the menus. :hoh

Rod · **Joined:** May 16, 2010 **Posts:** 14715 **Location:** USA

Actually i just noticed my scripts for fog and console show but will not execute...hrmmmmm weird.

Oregonian · **Posted:** Mon Jul 11, 2011 1:23 pm **(#3)**

Rod wrote:

Has anyone been able to get them to work.
http://registry.gimp.org/files/rendertexture1_3.py.txt

and

http://registry.gimp.org/files/bevel1_53.py.txt

I can not get either to even show in the menus. :hoh

The bevel one doesn't show up for me but the texture one does. When I tried to run it I got an error message.

Oregonian · **Posted:** Mon Jul 11, 2011 1:33 pm **(#4)**

Rod wrote:

Actually i just noticed my scripts for fog and console show but will not execute...hrmmmmm weird.

Both of them execute for me in 2.7.3 portable.

rich2005 · **Joined:** Mar 04, 2011 **Posts:** 2445

Using Gimp 2.7.3 & PCLOS 2011

They flag the same error as reported but work more-or-less.

screenshots http://i.imgur.com/iIw5s.jpg

gerard82 · **Posted:** Mon Jul 11, 2011 2:50 pm **(#6)**

I wonder where one could obtain a list of changed syntax/commands.
Both the scm scripts and python plugins can easily be changed in a text editor like notepad or a Linux equivalent
that has search and replace capabilities.
Gerard.

bilbo9955 · **Joined:** Jul 11, 2010 **Posts:** 349

At least they are showing where the error is and the new command to use in it's place. Also, they don't stop the plugin from working!

Rod · **Joined:** May 16, 2010 **Posts:** 14715 **Location:** USA

The strange thing is i can not get any Pythion scripts to run in 2.7.3 now. lol
Not even Shellout which is a must!...

So i have decided to re-install Gimp-2.7.3.
Results... everything now works

PhotoComix · **Joined:** Apr 12, 2010 **Posts:** 5870

gerard82 wrote:

I wonder where one could obtain a list of changed syntax/commands.
Both the scm scripts and python plugins can easily be changed in a text editor like notepad or a Linux equivalent
that has search and replace capabilities.
Gerard.

Often the error message is sufficent

search all the "gimp-image-add-layer" in the script and replace with "gimp-image-insert-layer" should solve

well sound a bit simplicistic and obviously will not work if the new procedure use a different number of type of arguments...but that is not so rare,

and in case from gimp you may open the procedure browser to search "gimp-image-insert-layer" or whatelse , documentation may be not updated but the short descrition there MUST be updated

JamesH · **Joined:** Apr 25, 2011 **Posts:** 78 **Location:** Taiwan

If you compile yourself
in order to get better smooth operation of the gimp
you could modify the function gimp_plug_in_handle_proc_run(app\plug-in\gimpplugin-message.c) as i do
use printf to display that message to the console window only

Code: Select all

static void
gimp_plug_in_handle_proc_run (GimpPlugIn *plug_in,
                              GPProcRun  *proc_run)
{
  GimpPlugInProcFrame *proc_frame;
  gchar               *canonical;
  const gchar         *proc_name   = NULL;
  GimpProcedure       *procedure;
  GValueArray         *args        = NULL;
  GValueArray         *return_vals = NULL;
  GError              *error       = NULL;

  g_return_if_fail (proc_run != NULL);
  g_return_if_fail (proc_run->name != NULL);

  canonical = gimp_canonicalize_identifier (proc_run->name);

  proc_frame = gimp_plug_in_get_proc_frame (plug_in);

  procedure = gimp_pdb_lookup_procedure (plug_in->manager->gimp->pdb,
                                         canonical);

  if (! procedure)
    {
      proc_name = gimp_pdb_lookup_compat_proc_name (plug_in->manager->gimp->pdb,
                                                    canonical);

      if (proc_name)
        {
          procedure = gimp_pdb_lookup_procedure (plug_in->manager->gimp->pdb,
                                                 proc_name);

          if (plug_in->manager->gimp->pdb_compat_mode == GIMP_PDB_COMPAT_WARN)
            {
              if( 0 ) 
                 gimp_message (plug_in->manager->gimp, NULL, GIMP_MESSAGE_WARNING,
                            "Plug-In \"%s\"\n(%s)\n"
                            "called deprecated procedure '%s'.\n"
                            "It should call '%s' instead!",
                            gimp_object_get_name (plug_in),
                            gimp_filename_to_utf8 (plug_in->prog),
                            canonical, proc_name);
              else // show message to console window only
                printf("Plug-In \"%s\"\n(%s)\n"
                       "called deprecated procedure '%s'.\n"
                       "It should call '%s' instead!\n",
                       gimp_object_get_name (plug_in),
                       gimp_filename_to_utf8 (plug_in->prog),
                       canonical, proc_name);
            }
        }
    }
  else if (procedure->deprecated)
    {
      if (plug_in->manager->gimp->pdb_compat_mode == GIMP_PDB_COMPAT_WARN)
        {
          if (! strcmp (procedure->deprecated, "NONE"))
            {
              if( 0 ) 
                 gimp_message (plug_in->manager->gimp, NULL, GIMP_MESSAGE_WARNING,
                            "Plug-In \"%s\"\n(%s)\n"
                            "called deprecated procedure '%s'.",
                            gimp_object_get_name (plug_in),
                            gimp_filename_to_utf8 (plug_in->prog),
                            canonical);
              else 
                printf("Plug-In \"%s\"\n(%s)\n"
                       "called deprecated procedure '%s'.\n",
                       gimp_object_get_name (plug_in),
                       gimp_filename_to_utf8 (plug_in->prog),
                       canonical);
            }
          else
            {
              if( 0 ) 
                 gimp_message (plug_in->manager->gimp, NULL, GIMP_MESSAGE_WARNING,
                            "WARNING: Plug-In \"%s\"\n(%s)\n"
                            "called deprecated procedure '%s'.\n"
                            "It should call '%s' instead!",
                            gimp_object_get_name (plug_in),
                            gimp_filename_to_utf8 (plug_in->prog),
                            canonical, procedure->deprecated);
              else 
                printf("WARNING: Plug-In \"%s\"\n(%s)\n"
                       "called deprecated procedure '%s'.\n"
                       "It should call '%s' instead!\n",
                       gimp_object_get_name (plug_in),
                       gimp_filename_to_utf8 (plug_in->prog),
                       canonical, procedure->deprecated);
            }
        }
    }
   ...

dd · **Joined:** Apr 10, 2011 **Posts:** 532

I don't have 2.7.3 installed, I've personally decided to wait for 2.8... so I'm not much help there. If anyone wants to make the changes to these scripts to get them to work smoothly in 2.7.3, please feel free to do so... just let me know and I can upload the 2.7.3 -compatible scripts on the registry pages.

GnuTux · **Posted:** Sat Jul 16, 2011 1:09 am **(#12)**

dd wrote:

I don't have 2.7.3 installed, I've personally decided to wait for 2.8.

No need to make changes twice, unless you have to. :hehe

Rod · **Joined:** May 16, 2010 **Posts:** 14715 **Location:** USA

PC that is a good idea.You could replace multiple sytax pretty easily with Notepad ++.

I may just start doing that with each script i run.Then copy each script to another folder.
It would be an interesting challenge.

PhotoComix · **Joined:** Apr 12, 2010 **Posts:** 5870

Did you do ?

Rod · **Joined:** May 16, 2010 **Posts:** 14715 **Location:** USA

No i think i am going to wait for the Gimp-2.8 to come out and let the writers fix their scripts to their own taste.

I tried with one python file and another invalid deprecated code error comes up with the same script.Evidently there are at least 2-3 deprecations or more for each file so i will wait. :lol

	Similar Topics	Replies
	error when running potrace	2
	Error when running Set Colormap script	1
	Gimp still running after an hour of closing it down	9
	SOLVED Wrong version of script running due to folder locn confusion	9
	very old scripts	11