5. User Events in Actor Framework (+ Chat Window Project Intro)

[@naderilahi2224]

Hi Tom , in the stopcore the user event has been destroyed , so I suppose that there is no refererence in order to unregister the user event. Could you please explain what do we make exactly with unregister user event , in other word, is ther an effect of not using it on the actorcore

[@TomsLabVIEWAdventure]

Hi Nader, Whenever we register events, we should also unregister events, this will allow LV to release references (a registration reference is different to the User Event reference). The references are different as you may have several event structures registered for an event (each with separate event registrations). This being said, my knowledge on how this work in the background is limited, so I would stick with the general rule of unregistering any events you register.

[@dmitrymelnik8296]

Hi Tom, thanks for the presentation. I have a rather trivial question. Is there any reason not to put "unregister for the events" inside the Events.stop case of the event structure (or whatever case which sources the true constant to the stop terminal)?

[@TomsLabVIEWAdventure]

Good question, and I suppose you could put the unregister function in the stop case. However, I've always put it outside the structure and loop so it's explicitly unregistered at the end of execution. That way you can change how the loop stops without having to move the function (not that that's ever been an issue!)

[@haojiegu7260]

Hi, The pre-launch vi is for creating a reference, isn’t it? Can we still create multi windows if we don’t have this vi?

[@TomsLabVIEWAdventure]

Pre-Launch Init.vi doesn't make the reference for the actor, instead, it is a placeholder for us (as developers) to (optionally) make references (such as user-event references). When you launch an actor Pre-Launch Init.vi will always execute, even if you don't make an override of it. The top-level Pre-Launch Init.vi is empty and doesn't do anything, but it will still be called and execute. So to answer your question, yes. You can launch as many actors as you want (multiple windows) without overriding Pre-Launch Init.vi. Does this answer your question? Hope this helps.

[@haojiegu7260]

Tom's LabVIEW Adventure tks, clear now

[@haojiegu7260]

Tom's LabVIEW Adventure tks, clear now

[@thaswikapazhanivel-diaries4147]

Hi Tom its very useful Thanks for your effort

[@denizkartal4620]

Very helpful, thank you for your effort

[@marcinborawski7033]

This guy is so funny but he doesn't do that on purpose, this is adorable how he rolls the eyes

[@TomsLabVIEWAdventure]

What can I say? LabVIEW has that effect on me 😉

[@yurik0spb]

why does the frequency rise in all clones whan you run launcher few times?

[@TomsLabVIEWAdventure]

Hi @ Юрий, I'm not sure I understand your question, is there a specific time in the video you're referring to? or could you elaborate please?

[@yurik0spb]

@@TomsLabVIEWAdventure sorry, wrong video. Look here kzbin.info/www/bejne/o6Ktont9fLmqmM0

[@TomsLabVIEWAdventure]

@@yurik0spb ah! That's interesting, I hadn't noticed that. I don't have access to the source code at the moment, but I'll look into it soon. Great question! I suspect that there is a shared resource (ie a non-reentrant VI) that is causing this behaviour. However, because I don't have the code in front of me I can't confirm that yet.

[@thaswikapazhanivel-diaries4147]

It will be great if you can share us the full code where users interacts each other for our reference

[@TomsLabVIEWAdventure]

All of the code I show is available on my github page, link in the description :)