LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

return to the previous step

I am making menu's with dialog buttons. When the dialog appears i have two options, (this is ok and cancel). If i choose cancel i want to go back to the first question, or the question before. How is it possible to do that. i included an example vi
0 Kudos
Message 1 of 6
(3,480 Views)
Hi,
here's a little modification of your VI in order to get the question again if the answer chosen is NO.
Tell me a bit more on what you need if you wanna get more precise answers. I'll be happy to help you.

VI modified with LabView 6.1. End condition of the while loop wired to output of first dialog box.

Hope this helps !
Julien
0 Kudos
Message 2 of 6
(3,480 Views)
IBI,

Julien's solution is the answer to your question. However, while you're
program is still small, it might be worth the effort to study a state
machine. This allows you to add this kind of functionality easily, even if
(when) it gets more complex.

Regards,

Wiebe.

"IBI" wrote in message
news:506500000008000000E2CF0000-1079395200000@exchange.ni.com...
> I am making menu's with dialog buttons. When the dialog appears i have
> two options, (this is ok and cancel). If i choose cancel i want to go
> back to the first question, or the question before. How is it possible
> to do that. i included an example vi
0 Kudos
Message 3 of 6
(3,480 Views)
Thank you very much for your help with the dialog boxes. I have another question, i want to do the same thing but this time with vi's.

I want to return from one VI to another. The problem is, that when i choose to go from one to another, i can't return. How can i solve this problem?

I am using labview 6.0
0 Kudos
Message 4 of 6
(3,480 Views)
You you are right because it gets complexer, but what do you mean with state machine. could you send it to me so that i can study it.

Thank you very much
0 Kudos
Message 5 of 6
(3,480 Views)
Hi,

A state machine is just a while loop with a case in it. The selected case is
determined by a shift register, that was filled by the previous state... An
example will clear this up.

If you search for "state machine" in the developer zone, www.ni.com, you'll
find lots of examples. The first you'll find:

http://zone.ni.com/devzone/conceptd.nsf/webmain/8C4EECACF084F8E986256802007B9186?opendocument

This one is ok, but I recommend using a "Type Def" enumerator instead of a
number or string.

You could consider using an array of states, so each state can add a number
of other states to the queue (queued state machine). This can get ugly (esp.
if you want to document it later on), but it is very flexible.

In LV7 you can make a state machine usi
ng an event structure instead of a
case structure. This can be handy, but can also cause a lot of problems. Try
a normal state machine first, then a queued state machine.

Regards,

Wiebe.


"IBI" wrote in message
news:506500000005000000497C0100-1079395200000@exchange.ni.com...
> You you are right because it gets complexer, but what do you mean with
> state machine. could you send it to me so that i can study it.
>
> Thank you very much
0 Kudos
Message 6 of 6
(3,480 Views)