Hello,
I am creating some custom step types that some other people will use and I have some information that i preferebly would like to store in them.
Some data shall be possible to edit from teststand more easily than others, for example if I create a step that sends information to an "address", address is here a number that the custom step in it's prestep sends to a certain UUT after it has been processed in some way. It would therefore be quite easy to change this step variable in a loop over that step and loop over a certain address range. I was in this scenario thinking of storing the information in a Step variable so that the "user" easily can modify it, is this a good approach?
I also need to store some data that the sequence editor "user" does not need to know so much about, for example some flags that are used during the execution. (but between different code adapters), so my idea was here to store theese as attributes in the step.
In this way this information is more hidden and wont be accidentaly changed when creating sequences, is there any performance issue by doing it like this or something else I would think about?
