2.3 Properties

  • Article

Three property blocks— OfficeArtFOPT record, as defined in section 2.2.9, OfficeArtSecondaryFOPT record, as defined in section 2.2.10, and OfficeArtTertiaryFOPT record, as defined in section 2.2.11, are associated with each shape instance. The OfficeArtSpContainer record, as defined in section 2.2.14, contains each of these property blocks. The OfficeArtFOPT and OfficeArtTertiaryFOPT property blocks, which are saved with the drawing group OfficeArtDggContainer, as defined in section 2.2.12, establish new defaults for every shape in the file. For example, if the fill color for the drawing group is set to red, any shape in any diagram that persists in the file without its own fill color will use red. If no fill color exists in either the document properties or the shape, the default fill color will be used.

If the fComplex flag of a property equals 0x1, that property has more data than will fit in the four bytes associated with the simple property types. In this case, the op field contains the number of bytes that follow the OfficeArtRGFOPTE records, as defined in section 2.3.1, and that contain the property data.

The structures that are specified in this section are supported at the file level by the applications, but not every application writes every property to the binary file. An application that does not fully support a property can load and save that property unchanged, which is the case for any property introduced in a later version of an application that is opened by an earlier version of the same application. Scenarios also exist in which a later version of an application supports a deprecated property or value by converting it to another property or value and then removing the deprecated one.

The following properties SHOULD<10> be supported:

The following property SHOULD<11> be supported:

The following properties SHOULD<12> be supported:

The following properties SHOULD<13> be supported:

The following property SHOULD<14> be supported: