09-08-2010 05:12 AM
Hi Ray,
unfortunatley this is not possbile, because when the step is created all parameters where empty. And If you do copy paste it maybe work,
but only with the old parameters not the new once.
I assume this is right way. I did some test with substebs "edit" and this might be a suitable solution. It looks like this
Do your parameter stuff in "Module" Tab after finishing next Tab there is the button "Edit" or "UpdateName" and just press it
then the name is updated.
The best would be if there is an "undocumented" function ,like OnNewStep was, it should sounds like OnModuleUpdate or OnModuleChanged
Maybe the "BlueOne" now something like this....
Regards
Juergen
09-08-2010 05:53 AM
Sounds like a TestStand Idea....
09-08-2010 10:25 AM
Hi Juergen,
In the example you gave, limit testing, this is something that the Numeric Limit Test that ships with TestStand does with the step decription field. I understand it would be nice to have it show up in the report too, and this is actually easy to do in recent versions of TestStand. You can add an additional result for the step description to your step type which will make it show up in the report. To do this, go to the General tab of the step type properties dialog and click the Advanced button and select the Default Additional Results menu item. In the additional results dialog, click on the button in the upper right hand corner and select "Step Description". This will add an additional result for the step description. One downside to Default Additional Results though is that it will not affect existing steps unless you have the files in which they exist open and check the "Apply Changes in this Dialog to All Loaded Steps of this Type" checkbox on the step type properties dialog box.
In summary, you could do something like the following:
1) Use step description expression to show parameter info the way you'd like.
2) Use an additional result on the step type to show the same, or similar data in the report.
One advantage of 2) above is that the additional result will actually have access to live data at runtime and so can actually show more than the step description does.
Just an idea. For your use case, perhaps edit substeps are a better option.
Hope this helps,
-Doug
09-09-2010 09:39 AM
Hi Doug,
Thanks for the hints how to add the description field into the report. It was a really good suggestion.
But my major task is to improve editing a step. At the monent you HAVE TO click, (or F2) on the step and rename it
except you like a lot of steps in the same name AND you have to specifiy the modules parameters.
What i have noticed is that on some SequenceCalls there is always a relation between its parameters and the
step.Name. So why should i not automate changing the step name?
At the moment substep.edit is my choice.
What do you think on adding a new call like "OnModuleValueChanged" which should be built in every moduleAdapater at all ?
Regards
Juergen
09-09-2010 10:12 AM
I think it's worth posting such an idea on the idea exchange and see what people think. I can see how it would be nice, useful to have the step name set automatically in some cases. Especially sequence calls since the most likely the name is something like "Call sequencefoo".
Perhaps these are really two separate ideas:
1) Having a setting to update sequence call names automatically (and perhaps other steps for which this would make sense too)
2) Having additional substep types to make it easier for step type developers to implement similar functionality
-Doug
09-09-2010 10:19 AM