I have some code that is writing to a device. The device will be changed but the same basic commands will execute (set frequency, set power etc). So, I have written a dynamic dispatch VI that takes a prebuilt command string and writes to the device appropriately based on which communication mechanism is used (SNMP, VISA etc). My question is related to the prebuilt command string that is fed to this VI. I feel that the VI creating the command string should also be dynamic dispatch, and should build the appropriate command for that particular device. But, some devices could have many parameters required to build up this string (for example, snmp) and something like VISA may only have one parameter. Dynamic dispatch VIs must have the same connector panes, so what is the best way to handle this? I thought about having a "parameters" class on the connector pane which held all the particular parameters for a device. But, it seems overkill to make a class for something like this, when a variant would do just fine as the input. However, having a variant like that tends to make me think dynamic dispatch isn't necessarily the right choice in the first place because you are forcing a similar connector pane.
I am also considering if some of the inputs are actually representing the state of the object and could be held in the object itself. This would minimize connector pane inputs and may alleviate some of these problems all together.
Thoughts?
