Jim, I got it this time around. Neat. Thanks.
Tore
At 13:27 5/27/2004, you wrote:
Tore,
If you are running on an RT Target, then the reentrant approach is better than the template technique, IMO. The reason is because of a "catch 22" -- you cannot create an instance of a template while the template is in memory; but, the template must be in memory in order to be transferred to the RT target when running in development mode (while targeting the RT system). In order to include a template into the build you would have to add it explicitly as a dynamic VI --> since it cannot be in the application hierarchy --> since you can't have it in memory when an instance is created at run-time. So, in conclusion, when spawning multiple instances of non-GUI processes, I highly recommend the reentrant VI approach in conjunction with the static VI reference to insure that the process VI is included in the application hierarchy. In general, most of my RT/embedded apps have been "headless" (set to run automatically at RT system startup time) and use TCP/IP to serve functionality to high-level GUIs. Since the server supports multiple simultaneous clients, this allows multiple instances of the same GUIs to be run concurrently.
-Jim
