You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
File ▸ Merge Returned Patterpack. Sending a project to a freelancer, a translator or a reviewer
has been a single file for a while (Export as Patterpack), but folding their work back in was a
terminal command. It is a menu entry now, and the round trip is three moves in the File menu: export
sends, Open Patterpack receives someone else's as a new project, and Merge Returned Patterpack
takes yours back. It asks for the pack that came back, then the pack you sent (the merge needs it
as the common ancestor), and shows you what it found before it writes anything, so you can back
out. Changes to different lines simply combine. Where you both changed the same line yours is kept
and a .patterconflict file is left beside the shard saying what disagreed. A file they added
arrives as it is; a file they deleted is left alone, because a missing entry in a zip is not good
enough reason to remove your work. It edits the open project and cannot be undone from the Edit
menu, so it says so and asks first, and your version control is the way back. If the two packs and
your project don't all claim the same project, it says so before anything else and makes Cancel
the default button, because that nearly always means the wrong file was picked at one of the prompts.
The name box offers the one your version control already knows. Patterpad asks for your name
on first run while a "Locked by someone" badge sits in the corner of the same window, which
means it has had a name within reach the whole time it was asking for one. It now fills the box in
with what Git, Perforce or Plastic calls you, ready to accept or type straight over. It is a
suggestion and nothing more: nothing is stored until you press Continue, and the box is simply
empty when your version control cannot say (or when you are not using any).
"Follow in the editor" on the Play window. The play window has always marked the line it is on
and left your place alone, which stays the default. If you would rather read the script as it runs,
the new toggle beside the pin asks the editor to reveal each line as it plays. Off until you turn
it on, and remembered after that. It never takes focus: the editor moves behind the play window,
so the keyboard stays where you are playing.
Fixed
Hover tooltips are back in the Play, Search and Coverage windows. Several controls in those
windows explained themselves on hover and had quietly stopped: the Search window's pin has had no
tooltip since 0.7.0, and the Play window's lost its own in 0.8.0. Every control in those windows
now shows the app's own tooltip rather than the operating system's slower one, matching the
editor. The Coverage window's pin also says what a click will do ("click to unpin" when it is
pinned) instead of always reading "Keep on top".