Did you ever find good resolution to more dynamic forms for calculator functions? I ran into that myself and ended up with a form that is probably more complicated than it needs to be. What is interesting is there are even some built-in calculator functions that could benefit from this. For example the psd function has a text box for entering a smoothing parameter which is only actually used by psd() when the window is set to Kaiser. I had a case where you could enter something in one of two ways but not both. An example would be entering a frequency or a period. I ended up using tooltips to say users should enter "nil" in either the "frequency" box or the "period" box. I would have preferred to have a cyclic to pick which and then have the form reflect that. I noticed that the documentation for the ahiCreate* functions all vanished in 617 so perhaps they are headed for removal at some point. Even if the form couldn't show/hide items, toggling the sensitivity would be helpful. Another example of the UI builder (which I basically like) limitations is a keyword argument that should always be set to a particular value when the function is used for the waveform calculator (causes it to return a waveform instead of a DPL which has the waveform and some key parameters). The more full version is useful in ocean. I could add a wrapper I suppose and just pass down all inputs and select the right output. That just gives one more thing to maintain. I did file a SR with some of this.![]()
↧