LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Julianne_K

When When Adding Multiple Events to a Single Event Structure Case, Make All Related Event Data Nodes Available - Presently Only the Common Event Data Nodes are Available

Status: Declined

Any idea that has not received any kudos within a year after posting will be automatically declined. 

When you create a User Event and add it to an Event Structure as an Event Case, you have new event data nodes available: the reference to the event and the data generated by the user event. Similarily, if you add a Control Event to the Event Structure, you have event data nodes available such as the old value and the new value. See the example of the User Event below: 

 

UserEvent.png

However, when you add two events to the same Event Structure Event Case, the UsrEvtRef and Demo Event Data Nodes are no longer available. Only the data nodes that are common between the User Event and the Control Event are available, as shown below: 

 

MultipleEvents.png

Merged.png

 

This behavior has been observed in LabVIEW 2011 SP1. Customers have expressed interest in being able to access user event data in Event Structure Cases which contain multiple events. 

Julianne K
Systems Engineer, Embedded Systems
Certified LabVIEW Architect, Certified LabVIEW Embedded Systems Developer
National Instruments
3 Comments
altenbach
Knight of NI

That would be useful, but what should be the output if the terminal does not make sense for the current event trigger. I guess the defaults for the datatype.

 

The idea should be more general and not just apply to user events:

Imagine I have an event case with a value change of a numeric and a cursor change of a graph. What would the output of the cursor index and cursor position event terminals be if the numeric value change fires the event?

AristosQueue (NI)
NI Employee (retired)

There is no meaningful "undefined" value for some of these parameters, especially user defined data. Even values like "NaN" might be legitimate values of the event. Combining events would be hard and would lead people to a more complex solution than is necessary. The easy and obvious solution is to put the events in different frames and use a common subVI for the common code. That's going to serve most users better than trying to come up with complex checks for undefined values, even if we found an acceptable solution.

Darren
Proven Zealot
Status changed to: Declined

Any idea that has not received any kudos within a year after posting will be automatically declined.