Jump to content

chrisempson

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0

About chrisempson

  • Rank
    I've come back for more.

LabVIEW Information

  • Version
    LabVIEW 2014
  • Since
    2010
  1. Thanks so much for your detailed reply, hooovahh. Your architecture makes a lot of sense, and removes the problem of having to wait for replies to messages. Doing a 1 to N message cast is a much better scheme in a distributed, asynchronous system. Your point about configuration data that is shared between Actors is a good one. I was planning on adding a hardware simulation option that all of the Actors would need to know about. I take your point about this architecture adding some undesired coupling, but that isn't a significant problem to me. Thanks again!
  2. Hi, I'm writing a LabVIEW application using the Actor Framework. This is the first time that I have used the framework and I need some advice regarding application architecture. My apologies if this is a basic question! How is a settings dialog box best implemented? In the past in non-Actor Framework applications I have loaded the configuration from a functional global variable, displayed the settings dialog, then written the updated settings back to the functional global. I'm not sure this would work correctly (or optimally) within the context of the Actor Framework, though. My a
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.