asbo

Have the VIs write their front panels to disk periodically and point your managers to the samba share.

It seems to me that if you drop a couple more For loops and split up your URL array you can use software parallelization to speed things up by having more nodes initiating connections while the rest are waiting to time out/receive data.

Can any executable do this? I don't recall ever seeing one able to differentiate. You can hack around it by enabling command line arguments in your build and then checking App:Command Line Arguments - you would have to enforce command line arguments in one scenario or the other to be able to figure how the executable was launched, however. I'm curious, what's your use case?

Ah ha! Probably didn't help that I built the test case wrong I'm reproducing this behavior in both LV2009 and LV2010, but one thing that I noticed that I don't think has been mentioned yet - if you grab the slider with the mouse, and then move off the slider to anywhere to drag back and forth, no beeping! But, I have no idea what that means

So if I understand correctly, the XControl should only ever beep once?

Will the default app instance work? You can pull an app instance from a VI ref, but from inside the RCF I expect it would return the JKI.LV.Extensions context.

I think the VM loophole gets around that one anyway

Were you looking for ASCII digits? It's entirely possible that it'd be stored in some binary format.

Sure, you just have to be competent in both languages. http://digital.ni.com/public.nsf/allkb/9018E4478599462A86256E8E0026F962 (P.S. This was the first result on google for "convert labview to cvi")

If you crack it open in a hex editor (or even Notepad ), it may have a reference to a particular version of the run-time engine. I don't have a DLL lying around, so I can't confirm this.

If you don't want to update data, you could also use unique indexes across the columns that would define duplicates. Duplicate records would simply be dropped, so this is probably faster than a replace. There's also INSERT ... ON DUPLICATE if you only want to partially update a record if the record already exists.

IIRC, Win7 (sometimes?) installs with a higher DPI selected; last time I reinstalled Pro x64 on my laptop, that was one thing I had to hunt down and fix.

For great search justice: "Error: Unable to contact wizard for this object. Deleting this object will destroy the wizard generated code. Press OK to continue."

That's a good point, the XOR is actually unnecessary. All in all, pretty slick.

Here's Ton's implementation. It shouldn't be too much of a stretch to make it temporal, just use a SR or a feedback node.

To clarify - you can right-click the graph terminal and select Create > Reference. This will let you drop a linked reference on the block diagram. Right-click that, and you can create either a control or indicator. Use those in your subVI and wire that reference into it.

You should be able to change each plot's name using a property node in the main VI. IIRC, you have to set ActivePlot first and then you can adjust all of the Plot properties.

You might check your Windows DPI setting as well. This seems more likely to me if you've already done a repair and uninstall/reinstall.

Sounds like an over-optimistic 80/20 to me

There's a disconnect in your own logic - if you have a numeric control on your FP, the wire coming out of it is only its value; not its radix, display format, color, size - any of that. Control and indicators are not variables, and while they are objects, their wire doesn't contain the object itself.

You're going to need to study up on signal filtering and come back with a specific question, the forums aren't really for homework hustlers.

http://i.imgur.com/RpIO0.png (Not embedded for vulgarity )

Remove the trailing square bracket: http://forums.ni.com/t5/Multifunction-DAQ/Update-Legacy-DAQ-sync-d-AI-AO-to-DAQmx-equivalent/td-p/1314635

It is, of course, not necessarily linear, but I wouldn't expect to be able to start installing stuff until lunch tomorrow after you've spent tomorrow morning cleaning up the aftermath