In message <3504AA7D.BC3D29D8@lynx.org>, Iain Hamilton <iain@lynx.org>
writes
>The easiest way I can think of to describe what I
>want is to compare it to a "GOTO" function. Finish
>a test and GOTO one of three options.
>
>I apologize if this is confusing but I hope I got
>the idea across
>
>Any help would be appreciated
>
>Iain Hamilton
>Base Maintenance
>Canadian Forces Base Borden
>Ontario, Canada
Hi Iain
It sounds like the sequencer object calling Dialog functions and
conditional jumping dependant on their return values is what might work.
Regards
--
Ger Murray
http://www.claycon.demon.co.uk/index.html
writes
>The easiest way I can think of to describe what I
>want is to compare it to a "GOTO" function. Finish
>a test and GOTO one of three options.
>
>I apologize if this is confusing but I hope I got
>the idea across
>
>Any help would be appreciated
>
>Iain Hamilton
>Base Maintenance
>Canadian Forces Base Borden
>Ontario, Canada
Hi Iain
It sounds like the sequencer object calling Dialog functions and
conditional jumping dependant on their return values is what might work.
Regards
--
Ger Murray
http://www.claycon.demon.co.uk/index.html
one of 3 or 4 choices in a multipart test (17
steps). Each step requires user input on the unit
being tested before they can carry on with the
next step (they have to change the channel on a
two way radio). After they change the channel,
they press a "Confirm" button to carry on to the
next test. I would like to put in the options of
canceling the test and resetting the program to
the beginning, repeat the last step or carry on to
the next step of the test.
START->SET TO CHANNEL 1->(TEST)->SET TO CHANNEL
2->(TEST) etc, etc
->REPEAT LAST
TEST->SET TO CHANNEL 1
->CANCEL->RESET ALL
I can automatically increment using different
methods, ie IF/THEN/ELSE and pushing parameters in
one test setup or "Confirm" buttons with each test
written out completely (BIG!!!). I have a trial
program setup up with an "Until Break", it
increments to the next test (one test layout with
parameters being pushed into it) but I can't
figure out how to make it repeat the last test
without adding what I would consider to be extra
"Confirm" buttons. Presently the user only has to
press the confirm button pertaining to the next
test, to put in the repeat feature, I can't figure
out how to avoid having a NEXT and REPEAT button,
where the user has would have to Start->Step
1->Next->Step 2->Next->Step 3->Repeat->Step
3->Next->Step 4 etc, etc..
The easiest way I can think of to describe what I
want is to compare it to a "GOTO" function. Finish
a test and GOTO one of three options.
I apologize if this is confusing but I hope I got
the idea across
Any help would be appreciated
Iain Hamilton
Base Maintenance
Canadian Forces Base Borden
Ontario, Canada