Closed OPerepadia closed 9 months ago
Indeed the order is:
I understand your suggestion and I will think about it, BUT the specific order can ONLY be set in the <TreeNodesModel>
section of the XML, it can not be deducted from the particular instance in <BehaviorTree>
BUT the specific order can ONLY be set in the
<TreeNodesModel>
section of the XML
Yes, exactly, this should be enough for our use case.
fixed
Is your feature request related to a problem? Please describe. When opening .xml files which contain nodes with multiple input parameters, Groot shows them in a different order (it seems in alphabetical, but I'm not sure). In a same way, when saving mission files in Groot, the order of parameters in .xml file is changed.
Describe the solution you'd like It would be good if Groot was able to keep the original order of input parameters. This would make it possible to put most commonly used parameters first, and add less used ones in the end of the list. Also, some parameters may be related to each other, so it make sense to keep them close to each other.