01-28-2010 10:00 AM
I did whip up a no-frills example of my approach at your request.
Test1.vi is a simple pop-up that is called to demonstrate any test. Its just a timer and a stop button no frills
Tests.ini is the configuration file that maintains a history of all tests available and the vi to launch (in this example I only launch Test1.vi)
Prompt.vi is a modified version of the prompt user express vi. I had to add a file path type that is not on the standard pop-up.
Main.vi
This section reads the ini and sets the Enums string property as mell as read the test file paths
I think the rest of the code is pretty obvious but--- ask if you have any questions
01-28-2010 10:18 AM
CAUTION:
I rushed a bit so I forgot
To set the VI properties on Test1.vi
Here it is corrected so your LabVIEW does not hang
01-28-2010 10:28 AM
More debugging
The event case Launch needs a few tweaks
an event case needed for the stop boolean
01-28-2010 10:37 AM
Short Name: Strings[]
If the string is an enumerated type control, you cannot write this property when the VI is running. If the string is a ring control, you can write this property when the VI is running.
Enum changed to Text Ring
Learning is fun
All functions work as desired
01-29-2010 01:19 AM
thank you alot
its all clear to me now ............if i will get any problem in future will tell you
regards
02-05-2010 01:31 PM
Actually, I got some value out of it too!
My customers ALLWAYS want just 1 more engineering function option to run from their production test systems (but only when they are experimanting for engineering purposes).
I just added a Pizza? boolean (what do you want on TOP of everything?) to my mainline GUI. Guess what it launches?