RSS/Atom feed Twitter
Site is read-only, email is disabled

Gimp2.4.0; problems with Script-fu

This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

3 of 3 messages available
Toggle history

Please log in to manage your subscriptions.

Gimp2.4.0; problems with Script-fu Ruud en/of Truus 28 Oct 14:14
  Gimp2.4.0; problems with Script-fu Aurore D. 28 Oct 16:03
  Gimp2.4.0; problems with Script-fu Kevin Cozens 30 Oct 04:15
Ruud en/of Truus
2007-10-28 14:14:00 UTC (about 17 years ago)

Gimp2.4.0; problems with Script-fu

Hi,

I installed de new Gimp 2.4.0.under Windows XP. It looks fine, but the Script-fu menu does not appear. The delivered scripts are present under the share directory. So it seems that the scripts contain syntax errors. I downloaded also the script Border3, which works fine under Gimp 2.2.17. After placing the script in the scripts directory the Script-fu menu appears in the image window. After applying the script border3 an error-message comes up. What to do about this problem?

Ruud

No virus found in this outgoing message. Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.15.10/1091 - Release Date: 24-10-2007 14:31

Aurore D.
2007-10-28 16:03:40 UTC (about 17 years ago)

Gimp2.4.0; problems with Script-fu

Hello,

installed de new Gimp 2.4.0.under Windows XP. It looks fine, but the Script-fu menu does not appear. The delivered scripts are present under the share directory. So it seems that the scripts contain syntax errors.

The menu where rearranged. Now there's no "Script-Fu" menu any longer. Instead, you'll find the scripts inside the various menus, most of the time in the "Filters" menu. (For example, the Coffee Stain script is now under Filters > Decor).

I downloaded also the script Border3, which works fine under Gimp 2.2.17. After placing the script in the scripts directory the Script-fu menu appears in the image window.

That's because that script was registered with the "old" style menus. The script tells Gimp that it should appear in a menu named "Script-fu", so Gimp create that menu.
If you're curious, you can search for "the script-fu-menu-register" part inside the script.

After
applying the script border3 an error-message comes up. What to do about this problem?

There were a few differences between the former and the new script-fu interpreters. You'll find the migration guide here [1], so you could search for the error messages in the guide and do the necessary replacements in the script. (I don't know that script, but maybe you could also try to see if the author made a 2.4-compatible version).

[1] http://gimp.org/docs/script-fu-update.html

I hope that helps :)

-- Aurore

Kevin Cozens
2007-10-30 04:15:39 UTC (about 17 years ago)

Gimp2.4.0; problems with Script-fu

Ruud en/of Truus wrote:

I installed de new Gimp 2.4.0.under Windows XP. It looks fine, but the Script-fu menu does not appear. The delivered scripts are present under the share directory. So it seems that the scripts contain syntax errors.

The Script-Fu menu is under the Xtns menu entry in the main tool box window. If you don't see that, you have a problem with your installation. You may not see a Script-Fu menu on the Image menu (depending on what additional scripts you may have installed) due to the restructuring of the menu system.

Many of the scripts and plug-in menu entries can be found based on what they do and not based on what language the script or plug-in was written in.

I downloaded also the script Border3, which works fine under Gimp 2.2.17. After placing the script in the scripts directory the Script-fu menu appears in the image window. After applying the script border3 an error-message comes up.

I can't help with your border3 script since you failed to state the error message that you saw. I would suggest you take a look at the Script-Fu migration notes located at http://www.gimp.org/docs/script-fu-update.html and see if there is something there which relates to the error you saw.