Tue Oct 18, 2011 4:35 am
Tue Oct 18, 2011 5:48 am
Tue Oct 18, 2011 5:31 pm
ofnuts wrote:Didn't try, but as far as I can tell there is no difference for your script. My python plugins appear in the PDB browser for script-fu, prefixed by "python-fu". That's about the only thing that would make them "special" from the script-fu side of the fence.
Tue Oct 18, 2011 7:52 pm
Tue Oct 18, 2011 9:14 pm
Wed Oct 19, 2011 12:52 am
Wed Oct 19, 2011 1:04 am
Graechan wrote:ofnuts wrote:Didn't try, but as far as I can tell there is no difference for your script. My python plugins appear in the PDB browser for script-fu, prefixed by "python-fu". That's about the only thing that would make them "special" from the script-fu side of the fence.
Actually it was one of your Plug-ins that I wanted to call, 'Random Elipses' and it definately seems different.
(python-fu-random-ellipse run-mode image drawable density overlap sizeAvg sizeVar flatAvg flatVar tiltAvg tiltVar)
If it were a Script I'd delete the run mode then place settings I wanted to use in my menu and define block the rest of the settings I'd assign a value in my (let* area.But what do you give for TRUE&FALSE.
Wed Oct 19, 2011 2:33 am
Wed Oct 19, 2011 2:59 am
Graechan wrote:Ofnuts your random ellipses_0.2 Plug-in is giving these errors whenever I run in 2-6-11The function works OK but the error codes are a worry.
Wed Oct 19, 2011 3:20 am
Technically speaking, Script-fu is considered an "extension", however, the distinction between an extension and a plug-in is to me rather elusive. If someone has a clear delineation of the distinction between an extension and a plug-in,
As was pointed out when Ofnuts originally announced this script, it breaks when run on Windows due to printing excess debug messages:
Wed Oct 19, 2011 3:27 am
Rod wrote:Didn't Ofnuts fix that though?Seems to me that he did.
Wed Oct 19, 2011 4:13 am
Rod wrote:Didn't Ofnuts fix that though?Seems to me that he did.
# v0.2: 2011-05-22: Enhance error message to track mysterious '9' bug
Wed Oct 19, 2011 5:49 am
Wed Oct 19, 2011 11:36 am
saulgoode wrote:The only special case occurs when you wish to execute another script from your script. In other words, when your script calls a PDB procedure whose name starts with "script-fu-". When this happens, Script-fu is already running (executing your script) and so there is no need to "run the Script-fu plug-in with the name of the procedure to run".
saulgoode wrote:There is no need to specify the 'run mod' because the invoked procedure will be executed by the same Script-fu interpreter/plug-in as your script and using whatever run mode that Script-fu plug-in was already using.
Wed Oct 19, 2011 12:26 pm
GnuTux wrote:That's the rub though, isn't it? If the interface to the interactive dialog can't be called while you already have a script running in the scheme interpreter, then the interface code lies outside the interpreter.
:
:
I'm not following you here. If an invoked script-fu procedure inherits the run mode, wouldn't it run interactively when invoked from a script that was initially ran from a menu (interactively)? Seems it could never run interactively, if there were no interface available.
GnuTux wrote:So in other words, a script-fu script can't call another script-fu script in interactive mode, no matter how it was initially invoked, correct?
Wed Oct 19, 2011 9:12 pm
Wed Oct 19, 2011 9:31 pm