First I need to understand why did you pass data to each of the UI elements instead of a real control which you can configure as you like?
If you pass a control you can use the PropSaver to get all the properties and move them to the chosen control on the FP.
You wrote something about avoiding property nodes since they make the UI flicker but I didn't have time to get too much into it.
Are you avoiding property nodes? I see property nodes in the setup control.vi of the ring for example...
Anyhow, If you are ok with it then my basic solution is setting the controls by using PropSaver on some off FP controls and allow composition of the controls properties by allowing to override location/size properties in your controls array, again, by enterring a control with the properties you desire.
If it was possible to turn a LV object to be the dynamic dispatch input of a vi the next step could have been simple and elegant.
I would then add a vi called "create control" with all the possible controls as input and create all the connected controls and maybe even allow an array input for each control type.
However, since you didn't do it, I guess I'm missing something here.
The other option is to create a long cluster with all the possible inputs and in addition an enum type. This cluster will be parsed and get you the same result as you currently have.
The added value of the PropSaver option is that you can add many more complex control types and the logic becomes much simpler with much less work on your side.
http://www.kshif.com/lv/
