Scripting - modifying existing polymorpic vi - dependencies issue

Question

I wrote a nice little tool using scripting to make it less tedious to create Polymorphic VIs for my libraries and functional global/action engine wrappers to make one interface for the functionality of the "object/data".  I hated having to click "Edit Name" for each individual VI selected, and hated not being able to add more than one VI at a time to the list.
I got that base create working beautifully, even setting the parameters such as "Show Polymorhpic VI Icon versus Instance Icon" working properly.
What is confounding me now is trying to add another VI to the list for an already created Polymorphic VI.  Opening the reference to the Poly is no issue, adding to the list of VIs is not an issue apparently - the problem comes when I try to Import Strings for the VI to modify the Menu and Selector Strings - the String file is formatted perfectly fine, but when I check the VI it is not using the settings as imported from the String File - when I used the Invoke Method of PolyVI - Get VI Dependencies and checl the Dependency Paths - the path returned for the newly added object subVI is the one for the previous VI - this seems to confound with the settings loaded by the Import Strings function.
There does not appear to be a way to modify the dependencies for the polymorhpic VI, only the Get is exposed....
What I am doing is taking a reference to the VI opened and casting it to Polymorphic, then using the same scripting node "New VI Object" to add the new VI to the Poly VI - the same way the original VI is built.  The only difference is that for a new VI I use the scripting node "New VI" to create the Poly VI  reference and Cast it as Polymorphic.  Using the Export and Import strings works perfectly to modify the Menu and Selector names in that instance.
I don't really expect an answer to be forthcoming as this is kind of a niche area - just thought I would throw it out there.  I can always use the built in Polymorhic VI editor to add new VIs to the list.
Ryan Vallieu
Automation System Architect
Solved!
Go to Solution.

Answer 1

So I haven't personally used it yet but over on LAVA there is a Polymorphic VI editor that looks like it is worlds better then the one build into LabVIEW.
http://lavag.org/files/file/136-polymorphic-vi-editor-v101-lv2011/
Using Polymorphic VIs is the only sanctioned NI way to make a VI handle multple data types.  And the editor they provide is so awful when you have more then a few types.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.