Working with slide masters

A slide master stores shared formatting and placeholder structure for a group of slide layouts. In PresentationML, a slide master is rooted at <p:sldMaster/> and is related from the main presentation part.

Slide master structure

Common child elements include:

<p:sldMaster
  xmlns:p="http://schemas.openxmlformats.org/presentationml/2006/main"
  xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships">
  <p:cSld name="Office Theme"/>
  <p:sldLayoutIdLst>
    <p:sldLayoutId id="2147483649" r:id="rId1"/>
  </p:sldLayoutIdLst>
  <p:txStyles/>
</p:sldMaster>

Navigating masters in Rust

Start at the presentation part and use the generated accessor:

#![allow(unused)]
fn main() {
use std::io::Cursor;
use std::path::Path;

use ooxmlsdk::parts::comment_authors_part::CommentAuthorsPart;
use ooxmlsdk::parts::presentation_document::PresentationDocument;
use ooxmlsdk::parts::presentation_part::PresentationPart;
use ooxmlsdk::parts::slide_comments_part::SlideCommentsPart;
use ooxmlsdk::parts::slide_part::SlidePart;
use ooxmlsdk::sdk::MediaDataPartType;
use ooxmlsdk::sdk::{OpenSettings, PackageOpenMode, PresentationDocumentType};

pub fn open_presentation_read_only(path: &Path) -> Result<usize, Box<dyn std::error::Error>> {
  let document = PresentationDocument::new_from_file_with_settings(path, lazy_settings())?;
  let presentation_part = document.presentation_part()?;

  Ok(presentation_part.slide_parts(&document).count())
}
}

For master-specific traversal, use presentation_part.slide_master_parts(&document). From a slide master, follow layout relationships with the generated slide layout part accessors where available.

Editing notes

Slide masters, slide layouts, and slides form a coordinated graph. A valid edit may require updating:

• the presentation part's master list,
• the slide master's layout id list,
• relationship items,
• content type overrides,
• the affected slide layout and slide XML.

Until a tested construction example exists in this book, prefer inspecting existing master/layout parts or copying a known-good package structure before making focused XML changes.