Hi,
the auto creation of dialog box for modules has to have at least one
input->required = YES; appearing in the "Required" Tab to build on the
fly.
Can somebody help me to remove this requirement.
I am building a module that does forward and inverse modeling,
(maybe that is why i.fft has a i.ifft sister module)
Cheers,
Yann
--
Yann Chemin
Researcher@IWMI
Skype/FB: yann.chemin
Yann wrote:
the auto creation of dialog box for modules has to have at
least one input->required = YES; appearing in the "Required"
Tab to build on the fly.
you can force a UI by adding "--ui" as a command line option.
Can somebody help me to remove this requirement.
I am building a module that does forward and inverse
modeling,
is it that you see "input" is required, or at least one required
option? the module typically runs with no options? (like d.erase
in grass6)
(maybe that is why i.fft has a i.ifft sister module)
i.fft transforms from geographic space to frequency space, and
i.ifft does the inverse, from freq. space to geographic space.
The two have nothing to do UI issues, the magic is you get to
work with the freq. space raster with r.mapcalc and all the other
raster array tools which don't know the map isn't a DEM or
similar.
but maybe I don't get what you mean.
?,
Hamish
The module had (i have split them in i.wavelet and i.iwavelet) no input required. When i enabled one input as required (actually a group input) then it built the dialog box.
I am making a temporal decomposer/recomposer using wavelet
Y
On May 17, 2013 5:47 PM, “Hamish” <hamish_b@yahoo.com> wrote:
Yann wrote:
the auto creation of dialog box for modules has to have at
least one input->required = YES; appearing in the “Required”
Tab to build on the fly.you can force a UI by adding “–ui” as a command line option.
Can somebody help me to remove this requirement.
I am building a module that does forward and inverse
modeling,is it that you see “input” is required, or at least one required
option? the module typically runs with no options? (like d.erase
in grass6)(maybe that is why i.fft has a i.ifft sister module)
i.fft transforms from geographic space to frequency space, and
i.ifft does the inverse, from freq. space to geographic space.
The two have nothing to do UI issues, the magic is you get to
work with the freq. space raster with r.mapcalc and all the other
raster array tools which don’t know the map isn’t a DEM or
similar.but maybe I don’t get what you mean.
?,
Hamish