If you have two sequence file where you MainSequence, one SequenceFile calls a Sequence contained in another Sequence File and you had set the option to Share FileGlobals then you can only Share if you are using Parallel or Batch Models. If you are using Sequential Model, although you can still set the option, the FileGlobals are still treated as separate.
The current Shared vs. Separate file globals setting is not related in any way to what process model you are using. I think the documentation incorrectly gives that impression, but its implementation has nothing to do with process models.
That said, I think you are misunderstanding what the setting does and are perhaps asking for a new setting. When using the Shared setting, the file globals are shared among all executions, BUT they are still per sequence file, so only sequences in the same sequence file can access the same FileGlobals. In the case describe above you are perhaps wanting the fileglobals to be shared between multiple sequence files. That is not how they currently work. Perhaps what you really want are station globals defined by the initial sequence file of the execution?
I know when I first started using TestStand (a long time ago), I created a number of sequences in separate sequencefiles because I thought it would be easier to reused sequences/sequencefiles this way only to find FileGlobals didn't work the way I thought they did when setting the Shared option.
I dont think you want them to behave like StationGlobals, otherwise you might just as well use StationGlobals.
I think you would need to beable to setup sequencefiles to beable to share FileGlobals from a master only at runtime.
Also, when setup sequencefile, have the option of to import the FileGlobals from a master sequencefile so that if used on there own they would not error because of missing FileGlobals.
regards
Ray
Message Edited by Ray Farmer on 06-15-2010 09:16 PM
I think what you want might be very similar to the another idea already posted, the Project-based or Workspace-based globals. Take a look at that idea and see what you think.
Another possibility might be to have a feature like we have for locals where a variable can propagate to the subsequence (that might be a lot trickier and potentially more confusing than the Project/Workspace-based globals though).
