Re: How to get Tracing in a Gimp Script?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Chad Jones wrote:
> I posted this to Gimp-User awhile ago and got no response. Hoping for 
> more here. :) Also, thanks Kevin for your earlier response! :)
> ----
> Earlier message:
> I am trying to turn on script tracing in Gimp 2.4 so I can track the 
> progress of a test script I wrote. Though I have called (tracing 1) as 
> indicated in the tiny-fu documentation I am seeing no tracing occurring.

There were changes to Script-Fu to deal with where it should be sending its
output. The problem is, Script-Fu can be used in several different ways each
of which has a different place where debugging output needs to be sent. The 
code to deal with that issue has been cleaned up but I'm not completely happy 
with where some of the output is going.

You're best bet is to use the GUI console and do tracing there. You can invoke 
a script manually, or you can define the variables the script needs, then cut 
and paste lines from the script a few at a time to watch the progress of the 
execution. Remember that if you have a loop in your code, you need to paste 
the entire loop code in one go.

Another, slightly better, alternative is to go to a terminal window and run 
GIMP using the command line "gimp -b -". This will give you a text console 
instead of the GUI one. Its better to use it if you will be tracing a lot of 
instructions (ie. you will be expecting a lot of debugging output).


Kevin.           |"What are we going to do today, Borg?"
Owner of Elecraft K2 #2172      |"Same thing we always do, Pinkutus:
                                 |  Try to assimilate the world!"
#include <disclaimer/favourite> |              -Pinkutus & the Borg

[Index of Archives]     [Gimp Developers]     [Gimp Users]     [Yosemite News]     [Epson Inkjet Printers]     [Scanners]     [Gimp's Home]     [Steve's Art]

&hbsp; Powered by Linux