copy event structure

[aSquared]

Hi,

I use LV DSC RT 8.2.1

Why can't I copy&paste an event structure together with his events specification (to the same VI)?

(I can create a copy of an event structure but his events specification are blank)

Is there a way to do it ?

Amitai Abramson.

[altenbach · Accepted solution]

Can you attach an example?

I can copy&paste an event structure just fine. Even ctrl+drag keeps all events intact.

[aSquared]

Hi Altenbach,

your solution is very good,

the event case is copy-able with CTRL+dragging

but not with copy & paste....

you can see the example I have attached

anyway thanks,

Amitai Abramson

[aSquared]

I have another question regarding the Event Case, (LV DSC RT 8.2.1)

I want to use multiple  Event Cases in a  Case Structure and sometimes for the same buttons.

It seems to not work and freeze the VI.

for example (in the VI 'Example2' attached) - If the user is in stage 0, so I want the button Boolean to do one thing,

and if the user is in stage 1, so I want the button Boolean to do a different thing.

In the VI Example3 attached (open it and press the Boolean2) you can see that the fact that you create an event that is in a

different area of the case structure handled causes the same thing.

If you just press the Boolean var then it is OK, but when you press Boolean2 it freezes.

( If you change to stage 2 before running, it will be opposite)

do you have a solution ?

Amitai Abramson.

[ssingh1]

You can do it like the attached vi.

[aSquared]

Hi ssingh1,

Thank you for your reply ,

but this VI is of a later version.

can you please save the VI in a version that I can open it ?  

 (I have LV DSC RT 8.2.1)

Thanks,

Amitai Abramson.

[ssingh1]

Here you go.   🙂

[aSquared]

Hi,

I still get this (see pic attached):

[ssingh1]

Ok Now Saved as version 8. Please try.

[altenbach]

---

Amitai Abramson wrote:

do you have a solution ?

---

Never hide event structures inside case structures. Event structures queue up events even if they are not in the datapath. Also, by default event are set to "lock the front panel until the event completes" (you can change that, but why would you?).  Since you fire an event that is not in the datapath, the event can never complete and the front panel will be locked forever! 😞

You also need an event for the stop button. This way you don't need to needlessly spin the loop via the timeout event.

Here's a quick draft, modify as needed.