I am a big fan of using Configuration EntryPoint callbacks to modify my process models in order to add items to Configure menu.
I find it a very convent way to bundle and provide additional wizards and dialogs that are useful for developers/end users of my test systems.
However, I am often puzzled by how TestStand determines what order to display menu items in when rendering Configuration menu for me. When manipulating menus via custom user interfaces, I often need to find the index of a specific menu selection in the configure menu, and have resorted to various API tricks / guess-and-check approaches but wish the order of items entered remained more consistent over time, as have burned several times by order of items shifting unintentionally when new ones are added.
I'm curious if anyone in community has ever come up with a simple way to explicitly define what index is always used by given Configuration EntryPoint that is easy to see/maintain?
I suspect it may have to do with where I right-click at the moment I create the new sequence in my model, since the fastest non-API hack I've found is to use cut-and-paste while carefully highlighting the last sequence already defined, and paste 'beneath' it when re-adding sequence to model file to enforce ordering... It feels crazy to think this is the 'easiest' way. but otherwise I appear to be obliged to maintain an API utility to read/shuffle sequences within the RunState.SequenceFile.Data.Seq array?
Would love to know if I'm missing something obvious.
-ElaineR
