This topic covers the implementation details of TPhysicalSections.
Scope: cpPhysicalSections.pas; class derived from TBLOB_Property. Prepared from the curated implementation supplied for this review on 2 October 2026.
Section children are searched consecutively from id=1, stopping at the first missing ID. The reader clears existing blob items before constructing each supplied section.
Notation and shared helper rules: Reading this reference.
Literal rec_type values emitted within these routines: TPhysicalSectionsBlobItem. Nested values may belong to child wrappers rather than this owner itself; the attribute entries below give their exact locations.
Structures used directly by this XML implementation:
Exact XML fields and attributes
The paths below start at this record or property node. A slash identifies a child element; @ identifies an attribute. Curly braces mark a variable index or expression, not literal XML text. Initial values describe initialization; they do not establish what an omitted individual element does. The Implementation toggle below contains the supplied routines for exact branch order and conversions.
Section/@id
XML representation: The id attribute.
Writing: Stores the text representation of (iB + 1) when for each iB from 0 through pred (ListBlobItems.Count).
Section[@id={(iB + 1).toString}]/@rec_type
XML representation: The rec_type attribute.
Writing: Stores the literal text “TPhysicalSectionsBlobItem” when for each iB from 0 through pred (ListBlobItems.Count).
Nested records and repeated elements
Operation |
XML location |
When it is processed |
Read aBlobItem |
Section[@id={i.toString}] |
while the record node exists |
Write aBlobItem |
Section[@id={(iB + 1).toString}] |
for each iB from 0 through pred (ListBlobItems.Count) |
Initialization and reset values
TPhysicalSections.Create
Setting or temporary variable |
Initial value |
When it is assigned |
PropName |
“Physical Sections” |
Always |
Required |
0 |
Always |
PropValue |
Default (TSL_PropValue) |
Always |
DataValue |
PropValue |
Always |
This routine also calls inherited Create; self.FillDisplayValue. See Implementation for their order and any conditional calls.
Storage declarations relevant to interpretation
These are in-memory member and property types, not a list of mandatory XML children. They retain array bounds, fixed buffers and selector types. The field reference above defines what is actually serialized.
The Implementation toggle contains only TPhysicalSections methods. Initializers and helpers belonging to other types are identified separately below. Shared XML-helper limitations are explained in Reading this reference.
