Table Of Contents


Last Modified: April 27, 2020

Actor Framework editor interactions have changed with regard to creating new Messages and Actors.

The Actor Framework in LabVIEW NXG includes the following changes:
  • LabVIEW creates Actors using a LabVIEW Library (lvlib) which consists of the Actor class and two virtual folders, Messages and Abstract Messages. LabVIEW NXG creates Actors as part of a component and groups Messages in namespaces instead of virtual folders. Converted Actors execute correctly in LabVIEW NXG. However, you must update your project architecture to ensure that the Message maker tools that automatically create Message classes function correctly.

    Actors in LabVIEW NXG must be part of a component with a namespace for the Message maker tools to function. If you attempt to use the Message maker tools outside a component, your application will return errors.

  • In LabVIEW, when creating abstract Messages you specify the data types for the Message data. If you change this data later, you can rescript the abstract Message to update the Message data. In LabVIEW NXG, update Message data by editing a type definition.
  • Actor Framework in LabVIEW has a shortcut create child of abstract Message. In LabVIEW NXG, you can use the create child class option in the right-click menu in the Project Files pane.
  • In LabVIEW, Actor Framework returns error code 43 for normal stop. In LabVIEW NXG, the normal stop error code is 1752.
  • In LabVIEW NXG, the Message maker tools for Actor framework are extensible only with C#.

What to Do

  • If your LabVIEW code handled error 43 for normal stop, you need to update it to handle error 1752 instead.
  • Review your project hierarchy to ensure Actors are properly organized in components with appropriate namespaces.

Recently Viewed Topics