06-25-2007 01:10 PM
06-25-2007 01:30 PM
BTW, I did do enum+variant based messaging before. In my version, formatting the variant was done by creating a typedef and a stub VI for each action, to force the user into entering the correct data.
Your version is definitely nicer in the sense that it does not limit the user.
06-25-2007 01:40 PM
The closest I have come to this is a cluster of enum plus string where the string is a flattened data structure that is un-flattened by the recieving agent that is indicated by the enum.
Unfortunately, many of applications require speed rather than re-usability so I seldom have a need to use this type of application.
Ben
06-25-2007 01:49 PM
@K1200LT rider wrote:
I'd love to see Nuggets based on OpenG VIs in the future. It's freely available to everyone, so why not?
- Brad
06-25-2007 04:32 PM - edited 06-25-2007 04:32 PM
Message Edited by shoneill on 06-25-2007 11:34 PM
06-25-2007 05:26 PM - edited 06-25-2007 05:26 PM
@shoneill wrote:
PS If NI is listening..... Native handling of this kind of thing is really the best way forward........ Hide the TDs for what I care, if I don't need the TDs for something like this and there are no (little) speed penalties, then that would be nice.Message Edited by shoneill on 06-25-2007 11:34 PM
Message Edited by Jarrod S. on 06-25-2007 05:28 PM
06-25-2007 05:38 PM
06-25-2007 06:05 PM
06-26-2007 01:23 AM
Here's an example.
The problems:
The main advantage is that it breaks these into modular components. You can use the stub VI on the other side to convert the variant back.
06-26-2007 02:18 AM