10-27-2011 09:46 AM
Hi,
I have a Sequences file, .seq, in which I have differents sequences. I use this file as a library (each sequence is a "function"). In this .seq file they is also a Callback sequence.
When I place a SequenceCall Step, in another .seq file which une this library, I can choose all my function sequences, but also the Callback sequence. How can I "disable" this sequence from the list of the sequences in the SequenceCall Step ?
Thanks for your help.
10-27-2011 09:50 AM
I would just delete it out of there. What's the point of having it if you won't ever use a Process Model with that sequence file?
10-27-2011 02:51 PM
I am trying to do the same thing for the operator interface - I want to only allow the operator to select sequences that are set up to be able to run independently. The way I figured out how to do it is a little tricky, and I think I may have found a bug.
This is what I did:
For the sequences I do not want to be selectable, I setPropFlags_Hidden to true. (Sequence Properties...Advanced...Flags, check the box).
This immediately hides the sequence. In order to see all hidden sequences to edit them, set Configure->Station Options...Preferences->Show Hidden Properties.
I wanted to set this up automatically for the sequence file, so I added a SequenceFileLoad callback to set ThisContext.RunState.Engine.StationOptions.ShowHiddenProperties = False, and a SequenceFileUnload callback to set it back to true.
The bug I think I found:
This solution works when I open the sequence file in the editor, but not when I use the simple operator interface. The simple operator interface will show the hidden sequences, but only the unhidden sequences show up in the RUN_SEQUENCE control. If I make sure the station is configured not to show hidden properties BEFORE I run the simple operator interface, then the hidden sequences are indeed hidden in the Sequences list (except, because I hid MainSequence, the first list entry shows up blank until I select one of the unhidden sequences).