Opened 5 years ago
Last modified 5 years ago
#5407 new defect
Make the input of array parameters a humane experience
Reported by: | casella | Owned by: | adeas31 |
---|---|---|---|
Priority: | blocker | Milestone: | 2.0.0 |
Component: | OMEdit | Version: | |
Keywords: | Cc: |
Description (last modified by casella)
Currently, the input of array parameters in OMEdit is a rather inhumane experience, particularly for beginners:
- it is not at all clear if the parameter is a scalar, an array, or an N-dimensional array, one has to guess or to look at the source code or at the documentation to find that out
- there is no (obvious) way to use each
- if a literal value is to be input, one has to get the syntax right
- even for advanced users, you may spend 10 solid minutes typing in
an elaborate literal array expression, hit return, and discover you
just lost all your work because of a stupid syntax error, e.g.
[3] 19:35:48 Scripting Error Unable to set the component modifier value using command setComponentModifierValue( BasicAeroEngines.Tests.TestTurboJet, fuelFlow.table, $Code(=[0, 0.4;]))
I would strongly suggest that we improve the end user experience on this front, at least in these directions:
- include some hint in the parameter window so as to the dimension of array parameters
- allow to use each from the GUI (mandatory with the NF)
- add a GUI for one- and two-dimensional array input
- check for the syntax validity before closing the input window, and in case of error give some error message but do not discard the wrong input, rather keep it available for correction
Change History (2)
comment:1 Changed 5 years ago by casella
comment:2 Changed 5 years ago by casella
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
See also #5405