Leaderboard

Thanks soupy, this works very well. It also is properly reported via the Desktop Execution Trace Toolkit. To simplify the code, I used a constant "Generic Event" with a variant data type.

Changing the password erases the undo history.

Memory leaks are caused by not closing registrations (event reg refnums) rather than user event refnums. If nothing is registered, you can generate your events 'till your hearts content and you won't leak memory.That's why you can have plugins that come in and out of memory and attach to existing events. Besides. When I exit, I want all memory cleared up including any leaks and LabVIEW takes care of that. When the app is running, I generally want all events running too and let whatever needs them regsiter and unregister..

here ya go. this only works if your cluster only contains user events but it'll close all data types. if your cluster needs to hold more than user events, you could probably get around things by storing user events in a sub-cluster.

Call the "Get Tag" method of the ProjectItem class and use the alias.value tag: