Select a list of tasks from a list and then execute the selected tasks

[quimper]

Hello,

from a list of possible tasks (ie do a wait, write a command ...), I want to select some of the tasks (one task could be selected several times) and then executes the selected tasks.

How can I do that ?

Regards,

Laurent.

[Norbert_B]

Laurent,

since your description of your question is.... well... at least in my opinion not sufficient for an answer, i can only guess. and the guessing a am doing here is, that you want to use a state machine. please take a look into the frameworks delivered with LabVIEW.

Norbert B.

[quimper]

Hi Norbert,

sorry for the previous description. I do not think this is a state machine I need.

I have a list of tasks (wait, do a write, do a read ..). Each task is a sub vi.

I want to select out of this list a sequence of tasks (ex: wait, do a write, wait, do a read).

Once I have selected the sequence, I want to execute it.

Laurent.

[Norbert_B]

Laurent,

this sounds a bit like the main functionality of TestStand

Nevertheless, perharps you should take a closer look onto the "queued message handler" architecture then. this fits in a more confeniant way.... each message "state" includes one subVI and the array of messages is built in the beginning by your interface.

maybe this helps a bit more

Norbert B.

[quimper]

Norbert,

I did find an example of a queued message handler architecture, the overall structure could somehow fit with my needs but it is mostly dealing with response notifier. May be I did look into the wrong vi ?

Laurent.

[quimper]

Hello,

the main issue I have is the following: once I select the list of tasks, I have a 1D array of string (ex: wait, do a write, wait, do a read).

Each string correspond to a vi and I want this vi to open when I click on the string (to change the parameters in the vi).

Do some one know how to do it ?

Thanks,

Laurent.

[Norbert_B]

Laurent,

reading your prerequisites confirms me in my opinion that you should use queued message handler as your architecture. I would create it in a following way:
there should be an "idle" or "User Interface"-case in the architecture which enables you to queue messages into the 1D-String-array which controls the architecture. after hitting a "run"-button, you would disable enqueuing and start off retrieving message after message from the queue executing the appropriate VI for each message until you emptied the queue or a certain termination-message is included in the queue.

hope this helps,
Norbert B.