paul_cardinale

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

View File paul_cardinale_xnodes-1.2.0.6.vip Here are some of my XNodes, packaged by Brian Hoover. Submitter paul_cardinale Submitted 04/15/2019 Category XNodes LabVIEW Version 2018 License Type BSD (Most common)  

Try this. Windows User Login 2017.zip

This works, but it uses a private property. Brs Btn Filter.vi

Just set the default value of the control.

As far as I can tell, lvstring.rsc is the only thing that contains "APP_SC_OPEN_EDITOR_WIZARD".

A long time ago (maybe around LV 7) I created a VI that was just a set of property nodes: One for every class (that I knew of), each node having every possible property. I think that when I created it, that property wasn't deprecated. All_Methods.vi All_Properties.vi

And that support would likely consist of: "Don't try to use that thing. It's broken". In general, there isn't an obligation to support undocumented features.

Is there really a need for that thing? If so, it wouldn't be very hard to create it as an XControl .