Leaderboard

A (perhaps) better solution is to release them on the NI's Instrument Driver Network. Then the source code is out there and available for anyone else to use/improve.

Actually it's A-ish. Files that are under the LabVIEW directory are "bucketed" in a LabVIEW folder. So from the example: A: application.exe/main.vi application.exe/subfolder/subvi1.vi application.exe/LabVIEW 2009/vi.lib/vilibVI1.vi application.exe/LabVIEW 2009/user.lib/_OpenG/openGVI.vi application.exe/LabVIEW 2009/instr.lib/Instrument Driver1/initialize.vi Adam is correct regarding writing your own wrappers. I believe that is mentioned in the help as well.

I had to test it to be sure. The answer is A (it also makes top-level user.lib and instr.lib folders if necessary). This means that if you call any of those VIs dynamically then you should also write wrappers for them in your own code to account for any relative path differences.

Yes, by default all VIs will go into the .exe using the same relative path between them as you had outside the .exe (you can, of course, tell the build spec to put specific VIs in specific locations using custom destinations). It finds the most common root folder of all the VIs and uses that as the top-level directory inside the .exe. If the VIs span drives on Windows then the top-level directories will be the drive letters. The one exception is vi.ilb, which gets its own top-level directory. This is to prevent common cases from having really deep hierarchies just for vi.lib VIs. This means if you call a vi.lib VI dynamically then you should write a wrapper VI for it in your .exe which you can then call using a relative path. The idea is to not have any code which has to check whether you're in an .exe or not in order to build different paths. The paths should always be the same.

Hi, It all depends on what you want to actually do with the split parts afterwards, there are several ways to skin this cat, typically you use the match pattern, match regular pattern , split string function in a while loop until you find no more matches. you can also do it all at once using the spreadsheet string to array.

Shaun, I have to apologize that I have not released a new package for the LVSpeak QuickDrop Add-on for LabVIEW 2009. I have already made the updates necessary to get it to work in 09 (easy) but need to work on making a clean distribution file (harder) If you still would like to use LVSpeak with QuickDrop before this package is released. Replace that file in your directory with the one attached after doing a backup of the working one. Your choice. QuickDrop Launch Window.vi

Here's a method that uses a relative path to open a VI reference. The VI reference allows you to manipulate the other VI at run-time. You can execute either VI, but because there is absolutely no communication between the VIs, they don't know which one started first, so both will be visible initially. As soon as you click the switch button, one will hide and the other will stay visible. This is just an example to illustrate the concept for you, you should not just plunk this down into your project and expect things to work spiffy. If you have questions about this method, fire away.

hooovahh Thank you This is exactly what I need but the solution is very complicated. Is there another simpler solution ?

Here's a quick and dirty way of doing what you want. It just shows or hides one window or the other based on a VIG. Run the Start Engines VI since it is the new top level one. It will run both the Login and Main windows. One will be shown the other hidden. Once the user presses the button on that window, it will hide itself and show the other, but they are both constantly running. EDIT: sorry I posted it in 8.6, now there is one for 8.5

QUOTE (dannyt @ Jun 1 2009, 12:54 PM) dannyt, Thank you for your interest this is what i need to do I have 2 VI files each of them has a button switch when you are in VI#1 and press the button VI#1 is closed VI#2 is opened when you are in VI#2 and press the button VI#2 is closed VI#1 is opened This is what I meant by switching between two VIs