[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[IDV #HIE-550438]: enhancement request Field Selector
- To: venus@xxxxxx
- Subject: [IDV #HIE-550438]: enhancement request Field Selector
- From: "Unidata IDV Support" <support-idv@xxxxxxxxxxxxxxxx>
- Date: Thu, 22 May 2008 14:38:04 -0600
- Delivered-to: support-idv@unidata.ucar.edu by laraine.unidata.ucar.edu (Postfix) with ESMTP id DAB2DCB1A1; Thu, 22 May 2008 14:38:04 -0600 (MDT) id B2D10D4FBA; Thu, 22 May 2008 14:38:04 -0600 (MDT)
> Hi Jeff,
>
> it works well.
>
> The tree-view interaction would indeed complement things. Further to this, I was wondering if the selection could also be done semi-automatically by matching the param-names used in a Formula against the names of fields available in the Field Selector.
>
> This would work analog to the "Search for a field by name" (as attached), except we have to consider the fact that some field %longname%s have spaces _and_ formulas would grow quite lengthy with many params. So a wildcards like * or ? would be helpful here:
>
> test(Retrieved?Temperature*[multiple=true])
>
> would auto-select all "Retrieved Temperature - Level x" fields, skipping the "Retrieved Moisture - Level x" fields.
>
That already exists. See the formula docs:
http://www.unidata.ucar.edu/software/idv/docs/userguide/tools/Formulas.html
You can also specify a regular expression pattern that is used to pre-select the first data choice whose description matches the pattern.
someProcedure(someValue[pattern=some_pattern])
Right now we only select one thing but I will look into it.
-Jeff
Ticket Details
===================
Ticket ID: HIE-550438
Department: Support IDV
Priority: Normal
Status: Open