02-09-2012 04:47 PM
This might sound crazy; but I was searching through methods and properties looking for a solution to do the following:
Does LabVIEW provide the tools to do this within it's vast array of pallets?
Step two is easy as long as the control or the parent cluster is not a strict type def.
G.R.
Solved! Go to Solution.
02-09-2012 04:52 PM
It should be possible to do this using scripting, but it will not be a trivial task.
Mike...
02-10-2012 07:59 AM
@mikeporter wrote:
It should be possible to do this using scripting, but it will not be a trivial task.
Mike...
But they says right there in the original post that step 2 is easy. (Hi Mike!)
The important point is the VIs that use the type def must be in edit mode or closed when the change is made.
Provided you are not using bundles (not bundle by name but bundles) they code may actully work after the change.
Ben
02-10-2012 08:02 AM
This is tedious, but straightforward using VI server / scripting. First, make sure the extra scripting items are turned on in the VI server options. Now, open the typedef like you would a VI. In scripting, a typedef is like a VI with no block diagram, only a front panel and control. You can get a reference to the control you need to change in one of two ways:
In any case, after modifying it, save it using the save instrument method and you should be good to go. The hardest part is getting the reference to the control. If you run into issues, let us know.
02-11-2012 03:55 PM
Thank you for the very useful information. Enabling VI scripting was the main key. My solution became a bit complcated because I was appending new elements to the string comboBox which was a strict type def contained by a strict type def cluster. Anyhow I have a solution that works.