The TestStand 4.0 sequence editor uses the ApplicationMgr just like the UIs. Thus you can still access ApplicationMgr.Executions. The trick is getting the reference. Here is how in pseudocode:
applicationMgr = (ApplicationMgr)engine.GetInternalOption(InternalOption_ApplicationManager);
You can do this from anywhere. It is a very useful technique. The application manager gives you a huge amount of programmatic control over the sequence editor and UIs. Note that this does not work prior to 4.0.
PS. Don't despair if you don't have an Engine reference in the location you want to do this. The Engine is a per-process singleton. Thus if it has already be created in the current process, you can get a reference to it just by creating it again.
Message Edited by James Grey on
11-16-2007 05:36 PM
