epics/pvData
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

Made sub-field/subfield consistent by changing to subfield.

Browse Source
This commit is contained in:
dhickin
2014-10-04 01:28:19 +01:00
parent e980823294
commit efbdb722e7
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
documentation/pvDataCPP.html
View File

@@ -287,7 +287,7 @@ ev4:nt/NTScalarArray:1.0
0x607188
</pre>
<h4>enumerated structure</h4>
<p>An enumerated structure is a structure with two sub-fields:
<p>An enumerated structure is a structure with two subfields:
index, which is an int, and choices, which is an array of string.
The following examples create a structure which has a field names value, which
is an enumerated structure and additional fields.
@@ -2481,10 +2481,10 @@ PVDoublePtr pvDouble = getPVDataCreate()-&gt;createPVScalar&lt;PVDouble&gt;();
<dt>createPVStructure</dt>
<dd>Create an instance of a PVStructure.
Three methods are provided.
The first uses an array of field names and an array of PVFields to initialize the sub-fields.
The first uses an array of field names and an array of PVFields to initialize the subfields.
The second initializes the subfields by cloning the fields contained in
structToClone. The newly created sub-fields will have the same values as the original.
If structToClone is null then the new structure is initialized to have 0 sub-fields.
structToClone. The newly created subfields will have the same values as the original.
If structToClone is null then the new structure is initialized to have 0 subfields.
The third method uses a previously created structure introspection interface.
</dd>
<dt>createPVUnion<dt>