PJM_labview

I think what JP Drolet is saying is that you have to make sure you have all the support libraries (whatever they may be) for your plugging VIs. One way to do that is to actually try to do a source distribution of your plugging including everything (VI.lib etc...). Your plugging VIs dont have to be part of executable distribution. PJM

In my opinion, the quit labview primitive should not be used. The application should be design to terminate nicely. As an example, you can use VI server and open a reference to your VI, open its front panel when require, then close the front panel and close the reference when you want to terminate your application. PJM

Ouch! Do they have one for paranoid too?

Nice Job and clean code :thumbup: Suggestions for improvement: Make a config window (and put all the config parameters in it) Make the whole UI very small and dock it somewhere on the side of the screen PJM

Woa! This was the last place I was expecting to see someone talk about Angouleme and Pineau des Charentes. I happen to be french (living in the US now) and I happen to be from Cognac. And guess what, I do have a bottle of Pineau des Charentes (made in Grande Champagne by Menuet [which is quite uncommun]) in my fridge at all time (you know for emergency situations). PJM

Yes, I have to agree, this got to be one of the best april fool joke I ever seen (Michael tone was perfect). May be to make it less realistic Michael should have announce that LAVA was beeing bought by Nabisco PJM

Just tried it a couple days ago, and it work pretty well. Thanks PJM

This is the oldest memorabilia that I got (although I start using LV at version 5.0 so I never had to enjoy the benefit of no undo ) PJM

The BD is like a "giant cluster", you have to traverse it to get all its objects. If you just get the SubVIs on the Top Level Diagram, you will not get the SubVIs inside structures. There is now a traverse utility in LV 8.0 to traverse BD or FP objects. The attached VI is using this. PJM Download File:post-121-1142291153.vi

good one. :thumbup: One can see that Mr Bill is not too happy at the of that clip...

Ed, It looks fine on mine (still shows in Bold). PJM

I will second Rolf post. If you can't figure out where to post, go post in the LabVIEW general forum! PJM

Yes I believe this is for representation. As a side note, the enum ctl has to be idle (not running and not in the call chain) for the string property to work. PJM

Well, the only idea that I have is that you may have a firewall setting somewhere that might be blocking the particular port used by the service locator. Good luck in resolving this issue. PJM

I dont think you can do that, but if you are using TortoiseSVN here is a work around (which may not be any faster). 1) Use the export function (right click over your folder>TortoisSVN>Export...) to export the whole directory structure to another folder (the svn folder are not exported) 2) Mass compile this new folder 3) Copy back (manually) the mass compiled files to the original folder under source control 4) Commit your changes Note: If I were you I would be very carefull not to do anything to these files in the .svn folder. You might end up damaging your repository. Good luck PJM

Make sure you have these 2 lines in your LabVIEW ini file: serviceLocatorEnabled=TRUE helpServerEnabled=TRUE PJM

Yes, I know this is not very intuitive, but you have to click on the black strip (this is where the color box is really) then the color chooser windows appears. After that the strip turn to the color you pick. PJM

Here is my contribution. By the look of them you can guess where I cast my vote. Note: the last one is "special" as it is a customized color box. PJM Download File:post-121-1140798932.vi

Floating somewhere on NI website is a VI with an embedded ActiveX control that does some voice stuff (I remember it did read text). I dont remember more about it, but this might be a good starting point. PJM

Or alternatively alway keep an empty (or with a space char.) free label sitting on your BD and just CTRL+Drag to make copy of it when needed. This should be very quick. PJM

I have seen a presentation by Michael Aivaliotis about LabVIEW 8.0 User Interface Tools and part of it was about splitter bar. I can tell you these splitter bar look VERY impressive. You get a lot of features for free (codeless). I can't wait to write an application in LV 8.0 that use splitter bar. PJM

When you load a VI in memory, LabVIEW will search for the subVIs in this order: - Memory - Subfolder form where the VI came from - VI search path (defined in the LabVIEW options) Therefore, for your particular problem, just reorganize your VIs the way you want, and then open your hierarchy (all the VIs) manually form the bottom up (the VIs further down in the hierarchy first) if possible. LabVIEW will automatically relink to the VIs already in memory. Once everything has been loaded, resave all your VIs to make the new linking persistent. PJM

I am aware that I can color the border. The issue is that, regardless of coloring or no coloring, you always end up with a minimum of 8 pixels between elements in your cluster. Below is a screen shot of your example slightly modified. PJM

You mean, like that? Download File:post-121-1139872010.swf PJM

If by reorder you mean change the order like you do in the editor (right click > reorder controls in cluster), then no, you cant do that programatically. But, you can always move the objects inside the cluster programatically (if you do that, make sure the cluster does not have "auto size" on). PJM