mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-10-24 09:46:59 -06:00
dotCooCoo
44c306f142
With the Artboard tool, File › Revert kept the active artboard, but a command.batch with a file.revert step made artboard 1 the active one. A batch that switched to another document and back, and the Actions panel menu's Batch… over a folder whose files it closes or over data sets with a Revert step, did the same. Each of them starts the tool afresh and ends in the document it started in, and the app moved the view to the fresh tool's artboard 1. Only a plain file.revert was handled, by its command id. The engine now counts the times switching or closing documents, or replacing the active one, starts the tool afresh (Session::tool_resets), and records whether the tool's options were set after that (Session::tool_set_since_reset). When the count changes during a command and nothing set the tool's options after it, the app starts the tool on the active artboard, as it does when a command chooses another document. When a later step chose the tool's artboards (a Paste or Cut after the revert), the artboard the tool then has active becomes the active one. Docs: docs/mcp.md, docs/target-app-parity.md.