02-22-2012 12:40 PM
Does anybody know how to create a table of parameters for a user to interact with (in edit time) for a custom step type? When you create a standard Action step, for example, with a LabVIEW VI, it gives you this nice table of parameters on the Module tab that are the ins and outs of your VI. You can enter values or variable names here.
However, when you create a custom step type with that same VI as a post-step, the table of parameters is embedded in the step and the user can no longer interact with the inputs and outputs of the step through that nice table interface. Perhaps this is good (in that you could have multiple VIs with lots of parameters, so how would the step know what to display and what not to display). But it would be nice to still be able to create a set of parameters for your custom step that the user could interact with. Presumably, in the creation of the custom step, you'd have to define how these parameters map to the ins and outs of the VIs that you setup as post-steps (or pre-steps, etc.).
02-23-2012 03:11 PM
Hi Erik the Red,
It is a little unclear exactly what kind of functionality you are trying to achieve. If you insert a custom step with the Labview adapter selected it will provide you with the same Module tab to configure the inputs and outputs. However, when calling a VI as a post-step of a custom step I believe what you are looking for might be the Edit Substeps that can be created for Custom Step Types. These substeps allows you create a portion of code that is able to be used to modify the settings of the step. The idea is to create a VI or external program which prompts the user for some settings and return those settings to the step. Some information on this process can be found here: http://zone.ni.com/devzone/cda/tut/p/id/2772. Also this article is a little older but might be of some use as well: http://zone.ni.com/devzone/cda/tut/p/id/3193.
03-19-2012 02:29 PM
Thank you for the reply, and sorry for my delayed response. I ended up speaking with a very helpful NI support engineer and have found a solution. Thank you for the links, I will have a look at them.