LabVIEW Idea Exchange

With how event source references are currently handled, it is not possible to add any additional event sources to an existing Even Registration Refnum. The user is required to know the number of events needed and statically configure the Register for Events block at the beginning. The Register for Events block is resizable when you have not wired an input for the Event Registration Refnum, as shown,

But this presents a problem whenever you are working with a preconfigured refnum. If you're working with an application that defines the events within a subVI and then passes out that Event refnum, there is no way to append new events to that refnum.

The new Register for Events is not resizable and there is no way to combine the previous refnum with a new refnum you have created. This really limits the capability to expand and continue using the refnum throughout your code.

The only ways to work around this would be,

Preallocate many readdressable events that you can later overwrite,

• Use a datatype that has multiple elements (cluster/array) and use the different array indices as needed

• Preregister many event sources on first creation of the refnum, and then rewrite over those sources later

The last way to approach would be to just create another Event structure to handle the new refnum.

Has anyone else run into something like this and has a recommended way to approach? Any other approaches and recommendations to help make the Event refnum more flexible would be great!

I'm shocked that this doesn't exist, but via help ticket verified that there is no way to do this (or they couldn't figure it out at least).

The following snippet shows what seems like would be close, but they are actually referencing VI's (none of these work):

What I'm after is figuring out the entire heirarchy above the current class level.  I solved this by making a method that passes out it's name and forcing overridden methods below the class.  This works well, but I'm annoyed that I have to create code for what is obviously available somewhere in memory already.

When you have the Desktop Trace Execution Toolkit (DETT) set to log errors, it will indeed generate an entry any time an error is generated. However if any custom message data is part of the error it is not captured, the DETT instead displays the default text for the captured numeric code.

I propose that this data should be logged as well.

According to the LabVIEW 2013 readme file (see attached image), NI installs a so called NI Launcher to work around serious shortcoming in the Windows 8 start menu. 

This is an essential tool because the Windows 8 start menu is flat (non-hierarchical) and if there are many NI products installed, the "all apps" screen shows pages and pages of tiles of e.g pdf help documents and it is impossible to find anything without scrolling forever.

Unfortunately, the NI Launcher functionality is quite limited to what we were used to be able to do in e.g. the Windows 7 start menu. All we can do is browse and launch a NI application.

While the readme suggest to pin often used program to the desktop, taskbar, or start screen, we can only do this by finding the icon on the Windows 8 "all apps" start screen first, where we can easily get lost if many NI products are installed! Yes, believe me, it is very tedious!!!

I suggest to add several right-click options to each entry directly in the NI launcher (similar to what we see in the windows 7 start menu):

• open
• pin to task bar (very important!)
• open file location
• troubleshoot compatibility
• run as administrator
• pin to start menu
• ...
•  (anything that is easily possible to implement)

 Idea summary: NI Launcher should have right-click options for each entry similar to the Windows 7 start menu.

.