jpdrolet

My pleasure... I seldom use VI datalogging for debugging purpose, when a VI goes wrong one run in a hundred. I datalog the VI and that allow to examine inputs and outputs of each run. It is fast and easy to turn on/off and less invasive than breakpoints. However, I've never used them for actual datalogging. Jean-Pierre

By defaul, VI images are in lossy JPG format. On the URL, you can specify to generate lossless PNG images. See here

Often I set the Desription and Tip of a control to the same text. An option to set them the same would be a time saver. It could work like the Item Tag and Item Name in run-time menus, that are synched until the user edit the Tag explicitely.

This bug was moved to the 7.1buglist forum Create a Combo box and enable the \ codes display. Enter a \ and continue typing. BSlashes are doubled every time you enter a new char until LabVIEW freezes. Is it Fixed in 7.1?

Similar to Scan from String, have unflatten functions a start index in the string and an offset past unflatten. That would simplify and optimize operations on flat data both in speed and string manipulation.

Sorry Jim (welcome back...) Set Contol Value {Coercable Variant}.vi doesn't work either... The Variant to Data node you use to perform coercion does nothing since you ask it to convert a variant to a variant... It is possible to make a VI that will coerce variant to another datatype (even numeric string to number...). You sent me an example once from a guy working on variants. I remember it was huge (~1MB) and then not very convenient.

Incorrect. The datatype must match exactly the control datatype when using Set Control Value(Variant). Unlike Variant to Data function, there is no implicit type conversion with this method.

There are many solutions. If you display one element at a time, you can enable/disable the control depending of the element displayed. If you display few elements, don't display the array but a subset of the array in a cluster where you can enable/disable elements individually. Or add an transparent/disable boolean indicator in the array element. Edit the boolean so that it is very small when false, and large enough to cover other elements when true (on top). Then you can "disable" the element individually by setting the covering boolean to True. This may not be convenient for large amount of data.

There are some limitations. I don't remeber the details now but you can't create a control on a ctl file. It must be a VI file. In LabVIEW 7 I once attempt to create/modify a typedef and realized after making all the hard work, it was not possible to make that on a ctl....

Having a single format to read C constants from string e.g "123" as decimal "0123" as octal "0x123" as hexadecimal

After reading temp-NRT.txt in step 3, do you close the file? If not then you won't be able to delete it in step 0 as long as it is opened. Anyway, keep the error outputs of steps 0 and 1 to see why the operation failed.

When connecting a new source on a wire (makes a bad wire), have the ability to automatically delete the wire from the current source (ctrl-Click). Possibilty to make this the default behavior for simple click.

Sorry for resurecting an old thread but can't you just use SystemExec to make sure LabVIEW is running? Or is the problem is to locate the LabVIEW directory?

To easily convert the time string to a time stamp, create a time stamp control with the same formatting as the time string. Then wire the time string value to the property Numeric Text>Text of the time stamp. It is like copying the string into the control. LabVIEW convert the value automatically. :thumbup:

The CINLoad() or CINInit() functions launching a shell command "labview.exe somecleverscript.vi" would allow to execute VIs as soon as the CIN node is loaded into memory. Possibly, a VI could execute code as soon as an instance of itself is created, then allowing some creative/evil scripting. Why do I feel like opening a Box of Pandora?.

Hi In a 2 step process, one can put a VI with the (attached) diagram on the palette with merge option. Step one is to select the vi in the palette and put it on the diagram.That will put code for the VI to call itself. Step two is to drag and drop the VI icon in the VI reference control to set the connector pane. It is possible by scripting to create the VI reference to match the pane of the caller, programmatically doing step 2. Now how to trigger this script when the code snippet is merged on the diagram? Would it be possible to intercept the merge call? One far fetch possibility is to add a CIN or CLN in the merged VI code and have the CIN(CLN) initialisation code (when loaded in memory) to execute the script. The script could also get rid of the extra CIN(CLN) node Any thoughts?