Programmatic access to SequenceCallModule.SequenceFilePath

[Oli_Wachno]

Hi there,

I was experimenting wtih ActiveX steps accessing SeqeunceCallModule. If the UseCurrentFile is TRUE,  SequenceFilePath is an empty string. If I uncheck UseCurrentFile in SeqEdit and put in the seuqence file's path and recheck UseCurrentFile, the following programmtic accesses to SequenceFilePath holds the corresponding string. This behaviour kind of caused me some trouble because I expected SeqeunceFilePath to hold the path, even if UseCurrentFile is checked... that's what it's like with expectations...

I've kind of worked around this issue, but I'd like to know if this behaviour is intentional?

Cheers

Oli

[Andre_Saller]

The property SequenceFilePath "remembers" the last path you entered or wrote via the API. If you set the UseCurrentFile to TRUE, the value is ignored, but not overwritten. ther same happens in the Sequence-Editor. if you enter a string, then check the UseCurrentFile Flag, and uncheck it again, the entered path appears again.

So this is the intentional behaviour.

To get the path of the used sequence file you would have to check the UseCurrentFile flag first. If it is checked, use the path of the used sequence, if it is unchecked, get the SequenceFilePath property.

[Oli_Wachno]

Thanks André

your suggestion is exactly what I took to solve this issue.

Cheers

Oli