dhendrix11

I'm working on a right click plugin but am running into an issue with grabbing the reference to only 1 item inside a cluster (can be front panel or block diagram constant). If I right click a single item inside a cluster, the right click 'Affected Items' returns 2 references: the reference to the item I selected as well as the parent cluster. However, if I multi-select 2 (or more) items, I do not get the parent cluster reference returned. It could be two items within a single cluster, or any two items at all. 'Affected Items' returns only 2 references. Best I can tell, it's impossible to identify when only a single cluster item was selected for right click manipulation. Bug, or am I missing something? LabVIEW 2019.

In this day any age, is NI package manager an absolute requirement for installing any NI SW? Our IT security suite is causing issues with NI package manager, and, until they fix it, it appears I'm unable to install any NI software. Is there an easy workaround I'm missing? Specifically, I'm trying to install NI VISA drivers. I've downloaded the offline iso installer, but it still wants to run things through NI package manager.

I don't have any immediate insights, but can at least confirm I see the same behavior on my system. Windows 10 64bit, LV2019.

No errors when running version 1.10.6. I am running my main actor directly, so I'll keep the renaming solution in my back pocket if I see the issue pop up again. Thanks for your help.

When updating Messenger Library from version1.8.3.82 to version 1.9.6.99, my application throws this error: Looking at the code I see the change that was made and comments pointing to here to explain the change: https://labviewcoder.com/2016/07/06/quick-tip-asynchronously-launching-vis-the-right-way/ If I change Dynamic Launch Shell.vi on the block diagram back to a strictly typed VI reference, the error goes away. What's gone wrong? The library has made my application development much easier, but I don't understand things well enough when an issue like this comes up. For now my solution is to backdate the library to the previous version, but I'd like to understand what's happening.