http://imagej.273.s1.nabble.com/Automating-Image-Processing-and-Problems-with-FFTJ-tp5004660p5004737.html
> >
> > That said, do you know of how the
> >>>> source ode of FFTJ would have to be modified to do the batch
> processing
> >>>> I
> >>>> need?
> >>>>
> >>>
> Aaron
>
> One way to make the code macro recordable/callable is to make sure all gui
> components (check boxes, options, etc.) are in a "GenericDialog". If you
> look at the FFTJ_.java file you can see several different types of dialog
> boxes being used. There is a "GenericDialog" as well as the
> "DisclaimerWindow" and the "OutputFrame". In the screen shot you attached,
> the "DisclaimerWindow" and the "OutputFrame" can be seen. These are a
> problem because they are not implemented in a way that communicates with
> the Macro framework.
>
> So my approach to make it recordable is to not show "DisclaimerWindow" and
> "OutputFrame" and place the options that were in the "OutputFrame" (Show
> real part, show imaginary part, etc.) into the GenericDialog.
>
> The changes are relatively simple so I put a "non-tested-example" on
> GitHub. If you look into the source code and compare FFTJ_.java to
> FFTJ_Scriptable.java you can see the changes that were made.
>
>
https://github.com/bnorthan/RogueImageJPlugins/releases>
> I use Eclipse but one suggestion I've seen (if you are interested in making
> changes to plugin java code) is to use Fiji and the *Plugins>Compile and
> Run *option. Easier to get started with I think.
>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>