Solution
When a user modifies the "Numeric Format" in the step settings pane in SeqEdit, it updates the "NumericFormat" property for the following four
:
-
Step.Result.Numeric
-
Step.Limits.Nominal
-
Step.Limits.Low
-
Step.Limits.High
To achieve the same behavior when creating a sequence file using the example "Building a Sequence Using API - XML.seq", you should set the "NumericFormat" for the above four properties in the XML as shown below:
<Prop LookupString="Limits.Low">0XC223</Prop>
<Prop LookupString="Limits.High">0XC233</Prop>
<Prop LookupString="Comp">EQ</Prop>
<Prop LookupString="DataSource">Step.Limits.Low</Prop>
<Prop LookupString="Result.Units">Hex</Prop>
<Prop LookupString="Limits.Low.NumericFormat">%#x</Prop>
<Prop LookupString="Limits.High.NumericFormat">%#x</Prop>
<Prop LookupString="Limits.Nominal.NumericFormat">%#x</Prop>
<Prop LookupString="Result.Numeric.NumericFormat">%#x</Prop>
Example:
Identifying Changes Made in the UI
To understand what changes occur when you modify a setting in the UI, follow these steps to identify the underlying properties that are modified so you can replicate the same:
1. Create a sequence file with a numeric limit step.
2. Create a clone of the sequence file and, in that copy, modify the numeric format using the UI.
3. Use the TestStand Sequence File Differ to compare the two files.
The differences will highlight all the changes made for modifying the numeric format. These are the changes you need to replicate to achieve the same.