paul_cardinale

Ok. As an alternative, is there a way to get the tab key to function as a tool selector on a block diagram that's in a SubPanel of a running VI? (It seems that the VI that owns the SubPanel is swallowing the keystrokes).

I want to turn AutoTool on. Shift-Tab toggles AutoTool on/off. That would be useful if there is a way to check the state of AutoTool.

Is it possible to programmatically change the inheritance of a LV class?

I'm working on a test executive framework (for both test execution and development). The test step editor places the block diagram of a test wrapper VI in a SubPanel. It works fine, but when the framework is running, within that panel, you can't change tools by tabbing. I want the test executive to turn on AutoTool selection so the test engineers using it won't have to.

Thanks for the reply. Close, but that will just toggle the state. I need to set the state to ON.

Is it possible to programmatically turn Automatic Tool Selection on & off? I found a ToolNumber property, but it always throws error 1028 (LabVIEW: (Hex 0x404) Attribute selector is invalid). I have no idea what that means.

Try this. ms path.vi

If you have a malleable VI (.vim) inside an XNode, and an instance of that .vim has a declined frame of a type specialization structure, and inside that declined frame you call a VI owned by the XNode, and you have a build spec that copies and renames the XNode, Then that renamed copy of the XNode will be broken because the item in the declined frame isn't properly linked.

Is this what you are trying to do? My Script.vi My Template.vi Setup Static VI Ref.vi

I'm pretty sure that you've built your block diagram incorrectly. Just do it right and it will work fine. (Since you didn't provide any code, I can't be more specific than that.)

Is this what you are trying to di? Scripter.vi Template.vi

View File UpdateState Illustration I think I've finalized my example for the XNode UpdateState ability. This is a very important ability. Failure to properly manage the update process can have dire consequences. Submitter paul_cardinale Submitted 05/14/2019 Category XNodes LabVIEW Version 2018 License Type BSD (Most common)  

When you are building a source distribution, if you run out of disk space while it's trying to write an XNode ability, it will throw Error 4 (End of file encountered), which is confusing. It should throw Error 9, disk full.

I've discovered that it's best not to put XNodes inside of XNodes (watch out for the NI XNodes like the Error Ring). If VI "A" depends on XNode "B", and XNode "B" depends on XNode "C", then if you save VI "A" for a previous version of LabVIEW, within that previous version, all instances of XNode "C" will be broken. The attached tool will dig through an XNode looking for dependencies on other XNodes. Check for Nested XNodes.vi