There are several instances that I have found where the name of an OpenFMB enum variant dropdown menu includes an option that ends with _UNDEFINED. For instance in the ESSControlProfile.mapping.essControl.essControlFSCC.essControlScheduleFSCH.ValDCSG.crvpts[0].mode.setVal.mapping[0].name the name choice has options for GridConnectModeKind_VSI_PQ, GridConnectModeKind_VSI_VF, etc. and one marked GridConnectModeKind_UNDEFINED. Is there a possibility for the end user to change the _UNDEFINED to something meaningful to the project?
I realize this may have been a poor example, but there are places with the same ending that I would have liked to change to a specific wording given the specific piece of equipment I am using.
There are several instances that I have found where the name of an OpenFMB enum variant dropdown menu includes an option that ends with
_UNDEFINED
. For instance in theESSControlProfile.mapping.essControl.essControlFSCC.essControlScheduleFSCH.ValDCSG.crvpts[0].mode.setVal.mapping[0].name
the name choice has options forGridConnectModeKind_VSI_PQ
,GridConnectModeKind_VSI_VF
, etc. and one markedGridConnectModeKind_UNDEFINED
. Is there a possibility for the end user to change the_UNDEFINED
to something meaningful to the project?I realize this may have been a poor example, but there are places with the same ending that I would have liked to change to a specific wording given the specific piece of equipment I am using.