We're working at creating our own Actor Framework for running on a real-time device, and we've had a few successes as well as a long list of "don't dos". Much like AristosQueue's actor framework, we create a queue of state objects that are dynamically dispatched in a loop. (We call these Execute.VIs, but they are essentially Do.VIs). We also have an Insert XXX.VI that does differ a little from the Send XXX Msg.VI. We create a unique Insert XXX.VI for every state that bundles in the state object's private data, but it does not enqueue the state, as with the true AF. Instead, it spits out a state object that is enqueue with a generic Enqueue State.VI. To create a cleaner look, we started to package states that don't have inputs into an Insert XXX.VI that has just a constant of the state class wired to an indicator. This works fine in debug mode, but an executable with this configuration does not seem to run. However, if we alter that state's private data by bundling something into it in the Insert XXX.VI, everything runs just fine in debug and execution modes. This behavior is always repeatable, which makes for an easy bug to solve, if this is in fact a bug...
Thanks for the help,
psyklopz
