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 331584 - Fix the Spyrogimp script
Fix the Spyrogimp script
Status: RESOLVED FIXED
Product: gimp-tiny-fu
Classification: Other
Component: Scripts
1.0
Other All
: Normal normal
: 1.0
Assigned To: GIMP Tiny-fu plug-in maintainer alias
GIMP Tiny-fu plug-in maintainer alias
Depends on:
Blocks:
 
 
Reported: 2006-02-17 18:22 UTC by Kevin Cozens
Modified: 2007-11-02 18:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kevin Cozens 2006-02-17 18:22:47 UTC 
The Spyrogimp script isn't working properly in Tiny-Fu as compared to Script-Fu. It might have something to do with the fact that the values for the inner and outer teeth appear in the dialog box with one decimal point showing in Tiny-Fu where they are shown with no decimal point in Script-Fu.

Is there a problem with the implementation of SF_ADJUSTMENT type in Tiny-Fu?
Comment 1 Kevin Cozens 2006-06-01 23:29:16 UTC 
The problem has something to do with the different interpreter used in Tiny-Fu vs. Script-Fu. Using the console mode of both Scheme based plug-ins I found there is a difference in the value returned from (calc-min-mult 86 70). Script-Fu returns a value of 3010 where Tiny-Fu returns a value of 64.
Comment 2 Kevin Cozens 2006-06-02 00:41:46 UTC 
Fixed the problem by using the tinyscheme lcm procedure instead of the scripts calc-min-mult. Need to investigate why calc-min-mult works differently in Tiny-Fu.

2006-06-01  Kevin Cozens  <kcozens@cvs.gnome.org>

        * scripts/spyrogimp.sct: Removed calc-min-mult procedure. Use the
        tinyscheme lcm library procedure instead. Fixes bug #331584. Changed
        defaults for number of teeth to match the values used in Script-Fu.
        Made tiny-fu-spyrogimp-internal a private procedure.
Comment 3 Kevin Cozens 2006-06-02 02:12:50 UTC 
The original problem was caused by an error in the fmod library procedure. The definition for this procedure has been fixed.