Feature Request: Have drop down options for ports

[tony-p]

Is your feature request related to a problem? Please describe.
Many input ports often require a valid value from a limited value selection, relying only on free input in these scenarios is fragile and requires intimate knowledge of underlying behaviour

Describe the solution you'd like
It would be great to be able to define options in the imported tree model that could then appear as drop down values in Groot. (Free input should still be allowed to allow for ports instead of constants)

<input_port name="port_name" default="default_value" type="std::string">Port description
  <option>Value_1</option>
  <option>Value_2</option>
  <option>Value_3</option>
</input_port>

This could be used to help solve enum sets (magic enum i already supported on an underlying level), but also string sets. I would also like to use this to inject valid ROS actions/topics/service addresses for node type into the tree model after initial generation to make them available in groot.

Describe alternatives you've considered
This is the only real valid solution I have thought of so far besides sticking with manual free input

Additional context
N/A

[facontidavide]

unfortunately, I see what you mean and why you suggest this, but I do not believe this is a good idea.

This UI approach would preserve the user from setting a blackboard key, instead of a specific value.

[tony-p]

It should be possible to support both right? IE have a free text field that can be optionally filled from a drop down menu. Or maybe it could be made slightly differently where you preserve the free text field, and when options are available an extra button appears that opens a menu/wizard/window that allows the user to select one of the options.

[facontidavide]

so, it is possible, and I see this being particularly valid for types like "bool".
But the change you are suggesting is not compatible with BT.CPP export and I am afraid it might be a little fragile.

I don't think I will add this yet