So we now know that Actors are really just object oriented Queued Message Handlers, and we know how to start the message handling loop of the actor and how to message that loop. Now we need to know how to actually get cool stuff done using actors.
A simple example that shows you how to build a basic Actor Framework based file logger.
Explain the not so easy task of getting this to work with the LabVIEW Database toolkit
Ever run into a Modal you forgot to close? Here are some tips & tricks when dealing with Modals.
MGI’s Class Method Broswer is a great tool for finding and using any of a class’ public methods.
Messages in the actor framework have a lot of boiler plate code. The built in message maker helps, but has room for improvement. The MGI Actor Framework Message Maker easily builds your actor message classes, but also:
This is the post excerpt. it should be medium length describing what the post is about.
See how you can use the MGI Monitored Actor Toolkit to get a live view of the actors currently running in your application
This LabVIEW Tip shows how the VI Server may be used to troubleshoot a built executable. The VI Server allows connections between instances of LabVIEW, with full functionality for LabVIEW development environments, and more limited
Boolean complexity hurts readability of your LabVIEW code, just like it hurts the readability of the title of this post. I’m going to illustrate some design choices you can make that improve readability without changing the functionality of your code.