Event structure with indicators

[BaSs_Garrido]

I want active the event with indicator, this beacause I am using a floating window where I change the datas and send it to main front panel, and I need active the event structure when the values change, I can't change the case structure by the main VI.

[Antoniooh]

You can trigger an event using custom events

https://www.ni.com/docs/en-US/bundle/labview/page/lvhowto/creating_user_events.html

[Antoniooh]

Also take a look at the fllowing document on recommendations when using events:

https://www.ni.com/docs/en-US/bundle/labview/page/lvhowto/caveatsrecmndtnsevnts.html#:~:text=Avoid%2....

[DailyDose]

As a 'rule of thumb' of event structures for beginners - an event should only be defined by a "user event."  Meaning the user did something.  If the data changes due to things you're monitoring - that should NOT trigger an event.  But a new state of a 'state machine' or queue up a case of a data handler.

[wiebe@CARYA]

---

@BaSs_Garrido wrote:

I want active the event with indicator, this beacause I am using a floating window where I change the datas and send it to main front panel, and I need active the event structure when the values change, I can't change the case structure by the main VI.

---

Pass control references of the controls (or indicators) on the main's FP. Then use a value (signaling) in the sub VI.

Alternatively, the floating window could be just a front panel (no loops, event structures). The main could start it and the main could register for it's (control) events.

[altenbach]

---

@BaSs_Garrido wrote:

I want active the event with indicator, this beacause I am using a floating window where I change the datas and send it to main front panel, and I need active the event structure when the values change, I can't change the case structure by the main VI.

---

I guess most have no problem understanding this and offer solutions.

I need to know more first:

So you have a caller and a subVI that has the panel open (not sure what else a "floating window" could be) and you want an event to fire when an indicator changes.

• Where is that indicator (caller or subVI)?
• Where is the event structure (caller or subVI)?
• Where is the case structure you mention
• How are you "changing datas".
• How is the subVI called? 
• etc.

Maybe if you could attach a small example program, I can give more advice. I have the gut feeling that you don't even need an event structure and are way overcomplicating things. Instead of telling us how you want to do something, tell us in more general terms what you are trying to achieve.

[billko]

---

@altenbach wrote:

---

@BaSs_Garrido wrote:

I want active the event with indicator, this beacause I am using a floating window where I change the datas and send it to main front panel, and I need active the event structure when the values change, I can't change the case structure by the main VI.

---

I guess most have no problem understanding this and offer solutions.

I need to know more first:

So you have a caller and a subVI that has the panel open (not sure what else a "floating window" could be) and you want an event to fire when an indicator changes.

• Where is that indicator (caller or subVI)?
• Where is the event structure (caller or subVI)?
• Where is the case structure you mention
• How are you "changing datas".
• How is the subVI called? 
• etc.

Maybe if you could attach a small example program, I can give more advice. I have the gut feeling that you don't even need an event structure and are way overcomplicating things. Instead of telling us how you want to do something, tell us in more general terms what you are trying to achieve.

---

I completely agree.  When the question is a rather odd one like this, sometimes knowing "why" is more important than knowing "what", since the real solution might be something completely different - and easier - to implement.

But then, we are responding to a post made last year.

[altenbach]

---

@billko wrote:
But then, we are responding to a post made last year.

---

Interesting. My reading got triggered by looking at a recent post from the same user that was equally vague, then checking what else he asked. I guess they did not advance much in a year. 😄

I only saw the 05-26 and stopped reading there, figuring it was recent. 😄 Bad form for a "numbers guy"....

[billko]

---

@altenbach wrote:

---

@billko wrote:
But then, we are responding to a post made last year.

---

Interesting. My reading got triggered by looking at a recent post from the same user that was equally vague, then checking what else he asked. I guess they did not advance much in a year. 😄

I only saw the 05-26 and stopped reading there, figuring it was recent. 😄 Bad form for a "numbers guy"....

---

I do that ALL THE TIME.  😄