ooth

Thanks for the replies. It's nice to know what the consensus of thinking is on references.

If you pass a control's reference to a subVI so you can edit its properties 1) should you close that reference in the subVI? 2) pass that reference back out of the subVI and close it in the main VI (even if you don't need to access it anymore)? 3) don't even worry about closing it because when the main VI exits the reference will be taken care of? I know it's good practice to close references I just don't know where to close it or if I have to?

QUOTE(yen @ Jul 27 2007, 08:54 AM) While Windows cannot gurantee timing, I was wondering if this is the same on Linux systems?

Yen, Those are very good points. I'll start using the Kind property now.

Here are some VIs that I use. I cannot find where I got them and I'm sorry to the author for not siting his/her work. The CallerIsExe.vi is the one that will help you. Just drop it in a VI and wire the Current VI's Path constant into it.

If you have the OpenG VIs you could open the VI located at LabVIEW 8.2\user.lib\_OpenG.lib\string\string.llb\Comment__ogtk.vi and change the color and font of the comment on the block diagram. That VI is just a merge VI that contains a comment. You could make your own merge VI if you didn't want to change the OpenG one.

QUOTE(Jim Kring @ May 15 2007, 05:50 PM) Thanks Jim for letting me know it's still there. I did have some issues when upgrading and it could have been deleted from my computer.

After I upgraded to LabVIEW 8.2.1 and installed the newest MAX4.2. and NI-VISA4.1, the visaconf.ini was missing. It used to be under C:\VXIPNP\WinNT\NIvisa\ but now it's gone. Just to remind everyone what was in that file, it contained the aliases to the COM ports and other devices: [ALIASES] Alias0 = "'COM1','ASRL1::INSTR'" Alias1 = "'COM2','ASRL2::INSTR'" Alias2 = "'COM3','ASRL3::INSTR'" Alias3 = "'COM4','ASRL4::INSTR'" Alias4 = "'LPT1','ASRL10::INSTR'" NumAliases = 5 So does MAX save the aliases to a different file? I use to dynamically write to this file with LabVIEW so the user could define their own aliases. Is there still a way to create an alias without using MAX?

I've had the same problem using LV8.2 and LV8.2.1. Hopefully someone has some ideas.

When I try to put the Xnode on the diagram LV says I'm missing "GetXnodeTermValue.vi". Should that VI be included in your llb or is it somewhere else? Thanks

Try this. I used the Top Left property.

I use the Move Window to Top.vi from the Windows Management VIs from NI. I'll attach them here. And here is a little program that demos it.

I don't have Professional just the Full version.

I always wanted the Path control to automatically resize to fit its contents so the user could see the whole file location. I made this little VI that uses a string method to vertically resize the Path control. I attached an example and the resize VI (version 8.2). Here's a pic of the code if you want to make your own VI in an earlier version. Download File:post-858-1167336674.llb

Here are some VIs that I use. I can't remember where I got them from. The Convert Seconds to hh-mm-ss.vi will probably do what you want. Download File:post-858-1157117403.zip

Don't worry about asking questions here. LabView can be confusing at first. Instead of using the "Insert Into Array" block, you just need to wire the output of the case structure to the array. When you bring a wire out of a For Loop it automatically becomes an array, shown by the square box I indicated in the picture.

Here's the VI I use to close modal windows. Hope it helps. I downgraded to version 7.0 for you. Download File:post-858-1150294026.vi

Structures (For Loops, While Loops, etc) will auto grow when you resize another structure that is inside it. This happens for all the structures except the Flat Sequence. Drop a For Loop on the diagram and then put a Flat Sequence in it. Grab the bottom edge of the sequence and resize it so it extends out of the For Loop. The For Loop won't grow! But it will grow if you use any of the other structures instead of the Flat Sequence. The thing is that I tried this in LABVIEW 7.1 and the loop did grow! So is this a bug in 8?