Hi!
(Setup: Teststand 2013 and LabView2013 on Windows7)
I want to start my UI (which is very close to the FullFeatured Labview UI) using the Development environment and pass the defined teststand command line arguments so that a seqeunce is started (after login). Somehow it does not work.
Start UI as EXE (working):
TestExec.exe /editor /run "StartupSequence" "D:\SequenceFile\Startup.seq"
Start UI as VI (not working, MyUi.vi does nothing more than calling the TopLevel VI of the FullFeatured UI):
Labview.exe "MyUi.vi" /editor /run "StartupSequence" "D:\SequenceFile\Startup.seq"
What did I do up to now?
1. I added code to the FFUI which shows me the cmdline args (App.args property ) of the Labview Application reference --> it shows the following string array (every array item in a new line)
LabView
/editor
/run
StartupSequence
D:\SequenceFile\Startup.seq
--> all arguments are passed like i write them on the command line excep the VI -> this is good because it is similar to the EXE situation.
2. I created a callback VI for the Application Manager Event ProcessUserCommandlineArguments --> Here I get an event for the command line item 'MyUi.vi' which means that the teststand AppMgr does not recognize this cmd line item. This is on one hand OK because the VI is not a known cmd line switch for teststand but on the other hand a little bit strange because the VI is not part of the string array I described under point 1!
Situation: sequence in given sequence file is not started, no error dialog appears.
Best regards
Waldemar