After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 109605 - Add ability to cancel Script-Fu scripts
Add ability to cancel Script-Fu scripts
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: Script-Fu
1.x
Other All
: Normal enhancement
: Future
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2003-03-31 14:10 UTC by Onno Kortmann
Modified: 2018-05-24 10:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Onno Kortmann 2003-03-31 14:10:06 UTC
Maybe I'm too stupid to find out, but the gimp should really have an option
to cancel the execution of a running script-fu script. Especially for
development, this would be very nice.
Comment 1 Olivier Ripoll 2003-03-31 14:41:27 UTC
Which script are you referring to?
I have tested a few ones here and there is always a window poping up
with a progress bar and a cancel button.
For plugins, there is the same cancel + progress bar utility at the
bottom right of the image window.
Maybe some external filter factory don't have this, but in thais case,
it is not really a gimp bug.
Comment 2 Onno Kortmann 2003-03-31 18:30:45 UTC
I'm refering to accidental looping to infinity in *developing*
script-fus. Things like "(while (= 1 1))".
Comment 3 Sven Neumann 2003-03-31 19:12:55 UTC
Would certainly be nice to have but not trivial to implement.
Comment 4 Alan Horkan 2003-07-23 18:39:07 UTC
Changes at the request of Dave Neary on the developer mailing list.  
I am changing many of the bugzilla reports that have not specified a target
milestone to Future milestone.  Hope that is acceptable.  
Comment 5 Michael Chang 2005-09-02 15:33:49 UTC
This sounds extremely hard to implement - for example, a script-fu can end up
opening and closing various files and displays, load various modal plugins, etc.
etc. -- where would you put the loop, and how would you break out?  What about
cleanup from stopping in the middle?  [Java, for example, deprecated functions
that stop threads in their tracks...]  I'd be willing to guess there are also
performance issues...

It might be easier to make effective use of the "ps" and "kill" tools on your OS
(or Task Manager, if in Windows) and avoid writing e.g. infinitely-looping
scripts in the first place.  I understand not everyone is perfect, but even if
such a feature was implemented, it might be relatively dangerous (Would repeated
init-stop that creates new images without cleanup cause memory overflow or out
of memory errors?).
Comment 6 Muthiah Annamalai 2007-01-19 01:40:07 UTC
Is this another instance of the Halting problem? Can Gimp guess when
programs will end?
Comment 7 Kevin Cozens 2007-05-12 04:27:38 UTC
Future plans for Script-Fu call for scripts to be run as plug-ins in the same way Python and Perl scripts are run. I don't know when this change will happen.
Comment 8 GNOME Infrastructure Team 2018-05-24 10:49:49 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/37.