1.0.13 — transitions animate again, and fonts survive copy-paste

[nyblnet]

1.0.13 is out, a day after 1.0.12 — because two people found bugs worth fixing immediately.

Transitions animate again

If you set a slide to Fade, Slide or Zoom, you got an instant cut instead. Three of the four transition types, silently doing nothing.

Reveal only keeps slides mounted within a set distance of the current one, and that distance was set to 1 — so the slide being moved to wasn't in the page at all, and the animation had nothing to animate into. Morph was unaffected, because that's Bento's own animation rather than Reveal's, which is why it never showed up in testing.

Broken for a long time — well before 1.0.11. Found, diagnosed and fixed by @7jameslondon, who also sent the before/after decks that made it obvious.

Copy and paste keeps your fonts

Copying elements into another deck lost their embedded typeface entirely. Copying whole slides was worse in a quieter way: it carried every font in the source deck, while leaving behind the bytes those records pointed at.

Both now carry exactly the faces in use, and if the target deck already has a font by the same name, its own bytes win. Fixed by @ShiroKSH, with a test rig that fails against the old code — so this can't come back unnoticed.

Update notes now cover what you skipped

The About dialog only ever described the newest release. If you were on 1.0.11 and updated straight to 1.0.13, you'd never learn what 1.0.12 contained.

It now spans the releases you missed. Anyone still on 1.0.11 updating today will see the laser pointer, the iPhone thumbnails and the count-up fix alongside the two above — each tagged with the version it came from.

If you missed 1.0.12 yesterday

A laser pointer while presenting (press L), decks that thumbnail properly on iPhone and iPad, count-up numbers that stop mangling thousands separators, the file you're editing shown in the tab, and every language pack complete — all 22, plus Turkmen.

Full notes: CHANGELOG · release

Thanks

Both fixes in this release came from outside, and both were things I'd have taken a long time to notice: one was a feature that had quietly done nothing for weeks, the other lost data in a way you'd only spot later, in someone else's deck.

If you hit something odd, please do file it — a repro deck is worth a great deal, and both of these arrived with one.

Questions in Q&A, ideas in Ideas, bugs in issues.