event structure triggered by multiple events

[mclaugb]

I have an events structure where one case needs to handle a button press from any of three controls from the front panel.  When i press any of the three buttons, the program is going into the correct event case.  However, once i am in the correct case, i need to know which button was pressed so that i can perform slightly different tasks?  Any ideas?

Kind Regards,
Bryan

[Jason King]

Part of the event data for each event is a reference to the object on which the event was triggered.  You can use this to tell which button the user interacted with.  Alternatively, if you're watching for Value Change, I suppose you can check the value of the buttons to figure out which one changed.

J

[dan_u]

Use the reference to read the label or something. See attached VI (LV 7.1).

[altenbach]

There are many possibilities. Attached is one simple example (LabVIEW 7.0) that does not use control references.

(If only one of the buttons can be active at any time. you could also use a single radio button as a control)

[falkpl]

Often when you want to trigger an event from multiple locations it is easiest to chain events.  That is to create an new event (USER EVENT) which takes the needed data (A cluster) that also includes the case or source of the event.  here you can handle the event in one location but fire it form multiple sources. 

Paul

[mclaugb]

Thanks for those.  I used the build array approach in the end.  I am somewhat weak on the property nodes so i found those the most elegant.  Are there any good resources or examples which explain property nodes?  Many thanks, Bryan

[mclaugb]

Paul, are you saying that one should bind the events and needed data into a cluster and wire that to the appropriate events case.  Once in the events case, then "chain" the event by parsing out the needed reference information from the cluster? Bryan

[dan_u]

Well, the property nodes come in handy on many occasions. For example, you can use property nodes to disable (and grey out) controls, to show/hide controls or to populate ring or listbox controls in runtime. In the example finder you'll find examples using property nodes.
To start, just right-click a control, select Create > Property Node and see what properties are available. With the context help enabled you'll see a short explanation of the selected property and possible values for it.

[falkpl]

Attached is a crude chained event.  The advantage of such an architecture is that you have a common event which can be triggered in from multiple places without forcing all sources to be treated as one event.  This also allows you to unrgistter each source independently and makes the code more flexable.  Just my opinion, I could be wrong.

Paul

[mclaugb]

Thanks for the chained events example.  That really helps me understand what you were talking about...it is a really nice solution.