mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-10-25 02:07:09 -06:00
dotCooCoo
c44fb242aa
Optical Margin Alignment was stored and set per text object, so the frames of one thread could differ. Turning it on in the first frame of a thread left the lines in the other frames flush with their margins. Type › Optical Margin Alignment and type.opticalMarginAlignment now set every frame of a selected frame's thread, in one undo step, and the reply's ids list them all. After any edit to a thread, its frames take the setting of the frame that the edit turned on or off, else the first frame's. Threading frames gives the thread its first frame's setting, and frames taken out of a thread keep it. A file whose frames of one thread differ opens with the first frame's setting in all of them. This holds for native files and for documents restored from the editing copy that an EPS, SVG, PDF or .ai file carries. Threading text from an out port into existing area type (text.thread.add with to) now flows the story into that frame at once. Before, the story reached it only at the next edit of one of the thread's frames. Docs: docs/mcp.md, docs/target-app-parity.md, docs/type-parity.md.