04-17-2007 03:40 PM - edited 04-17-2007 03:40 PM
Message Edited by TonP on 04-17-200710:38 PM
Message Edited by TonP on 04-17-2007 10:42 PM
04-17-2007 04:03 PM
04-17-2007 04:18 PM
Hi Tomi,
@Tomi M wrote:
Nice nugget Ton 🙂 One correction, you forgot to unregister you events in the end...
04-17-2007 04:30 PM
I beleave LabVIEW keeps sending even non-user events to event registration refnum "mailbox" as long as you have unregitered them or the main VI exits. This consumes both some processor power and memory and is not a good idea if you are not going to handle those events ever. So always unregister event registration refnum when you no longer need it. This is often done after the while loop containing the event structure exits.Hi Tomi,
I was not fully sure this was necassary, I thought this only was needed for user events because you have to destroy those.
04-17-2007 05:01 PM
04-18-2007 02:32 AM
04-18-2007 04:22 AM - edited 04-18-2007 04:22 AM
Message Edited by shoneill on 04-18-2007 11:23 AM
Message Edited by shoneill on 04-18-2007 11:23 AM
04-18-2007 09:12 AM
Hi Ton,
This really is a ton of stars worth !
I dont know at all about Dynamic Events since I ve never used these features in my work yet.
Hope to do soon after studying this nugget completely.
A Nugget in need is a Nugget indeed !
04-18-2007 02:56 PM
Nice nugget. I like using dynamic events to create UI handling subVIs for common UI functionality. You just have to supply them with a control reference and a boolean stop event and they can run as a seperate process.
@Tomi M wrote:
Even though event registration refnum can be wired to multiple parallel event structures, I strongly recommend not to do this. Always use an event registration refnum on a single event case only. Sharing event registration refnum would be similar to sharing a mailbox with a neighbourgh.
It's also buggy.
04-18-2007 03:32 PM