`<pic>` (Picture)

This element specifies the existence of a picture object within the spreadsheet.

[Example: Consider the following <SpreadsheetDrawingML> that specifies the existence of a picture within a document. This picture can have non-visual properties, a picture fill as well as shape properties attached to it.

<xdr:pic>
  <xdr:nvPicPr>
    <xdr:cNvPr id="4" name="lake.JPG" descr="Picture of a Lake" />
    <xdr:cNvPicPr>
      <a:picLocks noChangeAspect="1"/>
    </xdr:cNvPicPr>
    <xdr:nvPr/>
  </xdr:nvPicPr>
  <xdr:blipFill>
  ...
  </xdr:blipFill>
  <xdr:spPr>
  ...
  </xdr:spPr>
</xdr:pic>

End example]

Parent Elements
`<absoluteAnchor>` (§5.6.2.1); `<grpSp>` (§5.6.2.16); `<oneCellAnchor>` (§5.6.2.23); `<twoCellAnchor>` (§5.6.2.32)

Child Elements	Subclause
`<blipFill>` (Picture Fill)	§5.6.2.2
`<nvPicPr>` (Non-Visual Properties for a Picture)	§5.6.2.21
`<spPr>` (Shape Properties)	§5.6.2.29
`<style>` (Shape Style)	§5.6.2.30

Attributes	Description
`<fPublished>` (Publish to Server Flag)	This attribute indicates whether the shape shall be published with the worksheet when sent to the server. The possible values for this attribute are defined by the XML Schema boolean datatype.
`<macro>` (Reference To Custom Function)	This element specifies the custom function associated with the object. example: : A macro script, add-in function, and so on. The format of this string shall be application-defined, and should be ignored if not understood. example: < ... macro="DoWork()" /> The possible values for this attribute are defined by the XML Schema string datatype.

Attributes

Description

<fPublished> (Publish to Server Flag)

This attribute indicates whether the shape shall be published with the worksheet when sent to the server.

The possible values for this attribute are defined by the XML Schema boolean datatype.

<macro> (Reference To Custom Function)

This element specifies the custom function associated with the object.

example: : A macro script, add-in function, and so on.

The format of this string shall be application-defined, and should be ignored if not understood.

example:

< ... macro="DoWork()" />

The possible values for this attribute are defined by the XML Schema string datatype.

The following XML Schema fragment defines the contents of this element:

<complexType name="CT_Picture">
	<sequence>
	<element name="nvPicPr" type="CT_PictureNonVisual" minOccurs="1" maxOccurs="1"/>
	<element name="blipFill" type="a:CT_BlipFillProperties" minOccurs="1" maxOccurs="1"/>
	<element name="spPr" type="a:CT_ShapeProperties" minOccurs="1" maxOccurs="1"/>
	<element name="style" type="a:CT_ShapeStyle" minOccurs="0" maxOccurs="1"/>
	</sequence>
	<attribute name="macro" type="xsd:string" use="optional" default=""/>
	<attribute name="fPublished" type="xsd:boolean" use="optional" default="false"/>
</complexType>

<pic> (Picture)

`<pic>` (Picture)