Thanks for confirming that it works in 2.2 under Ubuntu and crashes on 2.4.
I too got that unbound error on 2.4 . I declared all the variables, which
cleared that up under Windows. I still got the unbound error in Ubuntu,
which is odd since set-pt is a function, not a variable??
So I added this in the hopes it would clear up:
; define the set-pt procedure (used to be embedded??)
; from http://adrian.gimp.org/scripts/shagadelic.scm
(define (set-pt a index x y)
(aset a (* index 2) x)
(aset a (+ (* index 2) 1) y)
This is added before the "(define (splineValue)"
It appears that set-pt is defined ("built-in?") in the Windows 2.4.1 build
but not Ubuntu 2.4?
However, with that function thus defined, the Ubuntu version behaves as
quirkily as the Windows version. Doesn't appear to do anything, but
proceeds to make GIMP act weirdly.
This odd behavior is why I am appealing for help. I appreciate your
On Nov 7, 2007 3:14 PM, <[EMAIL PROTECTED]> wrote:
> >> Following is my "Urban Acid" Script-Fu program. It attempts to
> > the
> >> famous Photoshop Urban Acid action, which dramatically alters the color
> > curves.
> >> The program worked well in GIMP 2.2, but is buggy in v2.4. I am having
> >> following problems:
> >> * The first time, it runs but the working layer shows no difference.
> > Indeed, even the mode is not set to overlay.
> >> * The second time executed, not seems to happen. Not even a copy layer
> > is
> >> created.
> >> * GIMP seems to increasingly act weird after that. Scripts may or may
> > not
> >> run. The entire experience looks like a memory over run.
> >> I am now running GIMP 2.4.1 under Windows, but I saw the same thing in
> > 2.4under Windows and also Ubuntu (Gutsy Gibbon).
> > Using Ubuntu-7.4
> > Gimp-2.2 the script works fine
> > Running on Gimp-2.4 throws the following error
> > Error while executing
> > (urban-acid 1 2)
> > Error: eval: unbound variable: set-pt
> > But I am not up with Script-fu so will leave debugging to others
> Ah ha, read some more mail, and this one from Tobias Jakobs points to the
> Script-fu changes which include;
> By far, the most common problem that can be expected if using an older
> script is that it might assign a value to a variable without first
> declaring the variable. SIOD-based Script-fu would permit a statement such
> as (set! x 4) even if 'x' had not been declared -- 'x' would be defined
> automatically to be a global variable. The new Script-fu protects against
> this situation and the programmer must declare the variable first. The
> offending script would result in an error message stating, "Error: set!:
> unbound variable: x".
> Gimp-user mailing list
Gimp-user mailing list