AnsweredAssumed Answered

User Options

Question asked by VRFuser on Mar 15, 1998

Like • Show 0 Likes0
Comment • 3

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

No one else has this question

Outcomes

3 Replies

VRFuser Mar 9, 1998 5:50 AM
Mark Correct
Correct Answer
I would like to be able to allow my users to make
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
Like • Show 0 Likes0
Actions
VRFuser Mar 9, 1998 4:24 PM
Mark Correct
Correct Answer
mvh
Bjrn Kristian Kleven
Ericsson Norway

Iain Hamilton wrote:

> I would like to be able to allow my users to make
> 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
Like • Show 0 Likes0
Actions
VRFuser Mar 11, 1998 5:15 PM
Mark Correct
Correct Answer
At 21:50 9/03/98 -0500, you wrote:
>I would like to be able to allow my users to make
>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
>

I imagine as follows:

a) You has so many global variables as different type of tests. Each of
these variabes is a text array in which it is included the number of steps
G_number_steps it is composed. For example:

      test1     test2
        2        1
        3        2
        4        5
        10       6
                 7

On the other hand, you has a global variable G_total_steps which represent
the number of total steps depending the type of test.

You could have a loop which input could be the total number of test that it
is selected when the user select test1 or test2 or test: from 1 to G_total_steps

You could have all steps codified as a function: step1 could be codified as
F_step1 with the corresponding (internal user inputs if applicable).

Into the loop you go to the cycle 1 and get (imagine you are in test1)
step2: therefore you call F_step2 to be executed. At the end of being
executed, with a junction you could push to continue or execute again.

What do you think about it?
______________________________________________________

Juan Carlos Martin
E-mail     : jcmar@mdr.indra-espacio.es
Phone      : 34-91-3963995
Fax     : 34-91-3963912
Earth Stations Department
INDRA ESPACIO / MADRID /SPAIN
Like • Show 0 Likes0
Actions

User Options

Outcomes

Related Content

Recommended Content