Leaderboard

I try to never miss out on an opportunity to toot Ton's horn when it comes to that XControl. Yes as already mentioned the Variant Repository that is available for download here is a VIPC, which contains the Variant Repository, and the Variant Probe. I included it because I felt that XControl really is a simple way to view variant data and it's structure, which is why it was included as an example showing how Variant Repositories work. When I give my XNode presentation, I start by explaining how they are related to XControls, and I use the Variant Probe as the example XControl. It's a perfect XControl, it's use cases are relatively small, you don't have lots of weird user interactions to worry about, and it displays data in a way on the UI that is more clear than any other native control. But do be aware that there is a bug with the Variant Probe, and updating it often in a loop will cause a very slow memory leak which will cause LabVIEW to take a longer than expected time to close. I reported the bug here but no new package has been made, so I just posted an update with the fix in the package.

I just realized this bug still exists and no update has been made. So for others that might be interested in using this with this fix applied, I made the fix and rebuilt the package. The spec has the version limited to >=2011 but I can't honestly remember what version I saved the VIs in and I only have 2015 installed at the moment. Variant_Probe-2.4.2-0.ogp

Through scripting? Looking at the available classes I think your only option is going to be to save a VI somewhere that has the register event callbacks configured the way you want, then programatically copy and paste them in. The reason I suggest this is because the Register Event Callback node appears as to be in the GrowableFunction class, and that has no methods (private or public) that can set the method of it. So the only solution I can think of is to make a VI that you'll use as a template, and it can have all the nodes configured the way you want and just sitting on the BD.

That's very good information, thank you! I kind of suspected this was a dead end. There seems to be a lot of potential for higher loop rates on the cRIO and this is an interesting thread related to this subject. http://forums.ni.com/t5/LabVIEW-Embedded/cRIO-Poor-Performance-Where-have-my-MIPS-gone/td-p/3026371