Edit Events should list only controls NOT an indicator-control

[richjoh]

OK, I don't know if this is already in the idea exchange but I can tell you it will save time after starting with a new project.  I attempt to add cases for indicators to the event structure forgetting that only controls are fired with event structure. Thus, only a control set to control (not indicator) should be included in the Edit Events list. Whenever I have a long break from using the event structure I keep falling into setting an indicator or a wired indicator to fire in the event structure. Removing indicators should remind use of this.

Anyone, fall into this ditch too.

[Darin.K]

Graphs are indicators and respond to a boatload of events.

The Picture Indicator is often turned into a 'control' using events.

The Value(signalling) property fires events for controls or indicators.

I must be missing something from your description.

[ThiCop]

Hello Rich,

But what if you want to trigger some action when you hover over an indicator?

[richjoh]

I'm not going to go through the gamut of events that fire and those that do. What can be done is eliminate or grey-out value change from Edit event if selected control is an indicator. Now if guys could put a list together of combinations that don't work well NI could implement the list with least privileges.

Well yes mouse over would work for an indicator, graphs etc, etc thats obvious but how about greying out value change in Edit Events list or the like that won't work.

[Darin.K]

---

@richjoh wrote:

...but how about greying out value change in Edit Events list or the like that won't work.

---

No gamut necessary, how about one example of an event that you can add but will not fire.  Value Change will work, simply changing value with the Value(Signalling) property will fire the event control or indicator.

[richjoh]

---

Darin.K wrote:

Value Change will work, simply changing value with the Value(Signalling) property will fire the event control or indicator.

---

Yes value change will work but IMHO Value(Signaling) is not a Value Change. (hushshsh, although thats what you can select, value change, or whatever in the Edit Event list). So unless you add more to the code to detect an actual value change you now go ahead and fire your property node Value(Signaling). No wonder I never or maybe once used Value(Signaling), it just fires away; add your own functionality, use of Signaling disclaimer....small print...Agreement.

Good point to remember though, my point still stands since its hard to keep nuances in mind.