Patterpad 0.33.0

Added

• Everything Patterpad does can be undone. Edit ▸ Undo takes back a Project Settings save (its renames
  included), a change on the Properties page, Replace, a new or deleted scene, a merged Patterpack, an imported
  editable script or translation, an accepted or rejected suggestion, shared scopes, the addresses Publish
  Bundle pins, a quick fix, the scene order, the start point, dictionary words, and writing status, recording
  status, re-record flags, and notes. They undo in the order you made them, mixed in with your edits to the
  script, and the Edit menu says what's next ("Undo Replace"). On the Properties page, Undo takes back the
  page's last change. If a file has changed since (a pull, or another app), Undo says which and stops rather
  than overwrite that work; if someone else has a file locked, it says who, and you can try again later.
  Comments and the suggestions you post aren't undone: they're a conversation.
• Renaming a cast member renames them everywhere. Change a name in Project Settings ▸ Cast, and every line
  they speak, their translated name and labels, and any extension data keyed by them or naming them follow it,
  in the same save. Before, their lines kept the old name and showed as a speaker who isn't in the cast.
• Patter extensions in the inspector and Project Settings. When a project takes an extension, its fields
  show in the inspector under the extension's name, after Game Data, for a line, text, game event, snippet,
  option, block, and scene: text, numbers, choices, flags, stages, references to other lines or scenes, and
  records, maps, and lists. Each shows its help, and a choice says what the picked value means. The project's
  own values have a section of their own in Project Settings, saved and undone with the rest of the settings,
  and it says which version the project takes and which game data field each setting names. A game data
  field an extension claims shows the extension's label and help, and says when its value isn't one the
  extension knows. Where someone else has an extension's data locked, its fields say who and can't be edited.
  Problems show under the field they're about, and Go to issue opens the extension's settings for a problem
  with the project's own values. A bubble whose extension data would be lost by merging it into the one above
  isn't merged, as one with a condition isn't: move or clear its data first.
• The problems bar shows a project's extension problems, under Extensions: a value an extension's manifest
  won't take, a claim on a game data field of another type, an entry for something that's gone, or a missing
  manifest.
• A project's Patter extension data travels with it. Deleting a scene deletes its extension data too, and
  a pack carries the project's extension manifests and data.
• An unresolved merge stays marked when you edit the scene. A merge that left a clash marks the files it
  touched, and saving the scene keeps that mark, so the clash can't be committed by accident.
• An option has Game Data fields of its own. Project Settings ▸ Game Data has an Option tab, and an
  option's fields are edited in the inspector like a line's, instead of shown read-only. A key no field
  declares, such as the Storyletter pairing's outcome, still shows as it stands.

Changed

• A game data value commits as you type, as every other field in the family does, and Esc puts back what it
  held. The inspector keeps your place as it redraws. Each field's purpose shows under its control instead of
  in a rollover, Flags are picked from the declared values instead of typed with commas, and a Text (multiline)
  field is a text area.
• Project Settings ▸ Game Data is the same declaration list as World properties and Storyletter's Card
  template: name, type, default, values or stages, and purpose in one row each, with the same controls. A
  field name is still any name you like.

Fixed

• Changing a qualifier's Game ID and renaming a game data stage in one Project Settings save works. When
  both touched the same scene, the save failed.
• Undo undoes what you're looking at. Edit ▸ Undo in the Search, Coverage or Play window undoes that
  window's own typing, and in Project Settings, a dialog, or on the Properties page it undoes the field you're
  in. Before, each of these undid the scene behind them, and on the Properties page that change wasn't saved.
  From the overview, Undo goes back to the scene and undoes there.

Security

• Every window carries a content security policy and stays on its own page: a window no longer navigates
  away, opens another window or attaches a web view.