[Table of Contents] [docx version]

PresentationML Reference Material - Table of Contents

cxnSp (Connection Shape)

This element specifies a connection shape that is used to connect two sp elements. Once a connection is specified using a cxnSp, it is left to the generating application to determine the exact path the connector will take. That is the connector routing algorithm is left up to the generating application as the desired path might be different depending on the specific needs of the application.

[Example: Consider the following connector shape that connects two regular shapes.

<p:spTree>

..

<p:sp>

<p:nvSpPr>

<p:cNvPr id="1" name="Rectangle 1"/>

<p:cNvSpPr/>

<p:nvPr/>

</p:nvSpPr>

..

</p:sp>

<p:sp>

<p:nvSpPr>

<p:cNvPr id="2" name="Rectangle 2"/>

<p:cNvSpPr/>

<p:nvPr/>

</p:nvSpPr>

..

</p:sp>

<p:cxnSp>

<p:nvCxnSpPr>

<p:cNvPr id="3" name="Elbow Connector 3"/>

<p:cNvCxnSpPr>

<a:stCxn id="1" idx="3"/>

<a:endCxn id="2" idx="1"/>

</p:cNvCxnSpPr>

<p:nvPr/>

</p:nvCxnSpPr>

..

</p:cxnSp>

</p:spTree>

End example]

Parent Elements

grpSp4.4.1.19); spTree4.4.1.42)

 

Child Elements

Subclause

extLst (Extension List with Modification Flag)

§4.2.4

nvCxnSpPr (Non-Visual Properties for a Connection Shape)

§4.4.1.26

spPr (Shape Properties)

§4.4.1.41

style (Shape Style)

§4.4.1.43

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

<complexType name="CT_Connector">

   <sequence>

   <element name="nvCxnSpPr" type="CT_ConnectorNonVisual" 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"/>

   <element name="extLst" type="CT_ExtensionListModify" minOccurs="0" maxOccurs="1"/>

   </sequence>

</complexType>