Add "Show Control" option to Event Registration Refnums on Front Panel

[_carl]

When in the front panel, most LabVIEW data types that wrap other data (such as arrays, DVRs, maps, sets, user events, etc.) allow you to directly view and modify the wrapped data.  For some of these data types it is not the default behavior, but it is available if to right-click on the control and select "Show Control...".

For illustrative purposes:

In all but one of the cases above, I can see that the underlying data type is a boolean, and I can swap this out easily for any other data of my choosing, such as a typedef.

The one exception: event registration refnums.  There is no "Show Control" option, and from the front panel it is impossible to update this underlying data type. Instead, you have to create a new event registration refnum in the block diagram. I do find that this makes it difficult to work with, maintain, and debug event registration refnums when maintained in class data.

The request: treat event registration refnums like any other data container type, and expose a "Show Control" option that makes the underlying data type accessible in front panels.

[fefepeto_kb]

It might be something that I misunderstand, but the Event Registration Refnum is not a container. It is a type, that describes all the event registration refnums. Actually, you can create an event registration with multiple ActiveX or .Net Framework objects and methods in one node and the type of the refnum won't change.

[wiebe@CARYA]

@fefepeto_kb

That's pretty accurate. The event registration can have all kind of events bound to all kind references (.NET, AX, user events, VI, application, controls, even DAQmx IIRC).

Each individual event can be registered not only by reference, but also by a cluster or array of references, or any nested combination of them.

On top of that, there are right click options that can be set for each registered event (like "Lock Panel..").

This could still be shown as a control, but it would be a lot...

The same objections (exposing encapsulated information, although that was never one of my concerns) might apply: Allow "Register for Events" to have a "Read events" version to unbundle user events - NI Community

[_carl]

Yep, fair point guys! I was working with a pared down case: an event registration refnum created from a single from-data-generated user event. In that world, this would be quite useful.  But it escaped me at the time that yes, of course, you can have multiple user events in an event registration (and not-data-type-based events too) -- and...well...that gets complicated to illustrate with "show control" very quickly.

Jumping on the bandwagon and shooting down my own idea!