deploy.

2026-09-12 18:16:27 +08:00
parent b7f55aa631
commit 397a7a8cc4
96 changed files with 1167 additions and 1259 deletions
@@ -89,8 +89,9 @@

 <p>The settings that follow the application rather than the project are kept on two sides: the service,
 where one value serves every browser signed in to it, and the browser, for the device it is sitting
-at. The <strong>Preference</strong> menu is where most of them are set, and the rest are reached from the panel
-each one belongs to. Which side keeps a setting is the thing worth knowing about it, because that is
+at. The <strong>Preference</strong> menu carries four of them — the language, the physics switch and the two
+controller checkboxes — and the rest are reached from the panel each one belongs to. Which side
+keeps a setting is the thing worth knowing about it, because that is
 what decides who else sees the change.</p>
 <h2 id="where-it-is">Where it is</h2>
 <p>The <strong>Preference</strong> dropdown on the menu bar, after <strong>Project</strong> and <strong>Page</strong>. It carries no OK and no
@@ -126,9 +127,11 @@ for a selected step, which of that page's charts, its <strong>Session Messages</
 Properties</strong> panel are switched on, the General Setup canvas's display options including the work
 coordinate its marker draws, and the graphic cache budget.</p>
 <p><strong>The browser keeps the arrangement of the screen in front of it.</strong> That is the two tree pages'
-layout — which columns are shown, how wide the docks are, which tree nodes are left unfolded and
-which node each tree page reopens on — together with the two controller checkboxes above, and the
-File Explorer's editor pane, its split and its sort order. Three of the Execution page's panels sit
+layout — which columns are shown, how wide the docks are and how the right-hand dock is divided
+between its two columns, how tall the editor row under each tree is, which tree nodes are left
+unfolded, which node each tree page reopens on, the heights dragged between stacked panels, the two
+shared chart legend widths and the shared strip-chart x-axis mode — together with the two controller
+checkboxes above, and the File Explorer's editor pane, its split, its auto-save and its sort order. Three of the Execution page's panels sit
 on this side rather than with that page's others: the <strong>3D Rendering Canvas</strong>, <strong>CWE</strong> and
 <strong>Sentence Syntax</strong>. The browser also holds a copy of the language, used only to paint the first
 frame before the service can be asked; the service's value wins every disagreement, so a language
@@ -139,15 +142,17 @@ reaches the service's preference file only when some later preference save write
 service stopped before any such save comes back on the budget it had before.</p>
 <h2 id="making-a-physics-change-take">Making a physics change take</h2>
 <p><strong>Show Physics Options</strong> is read while a tree or a tab row is being built, not while one is on screen,
-so the four routes below are what the tree and the tab row need; the two canvases pick the change up
-on their own next draw instead. Ticking it therefore changes nothing already built: the tree does
-not grow the nodes it gates, and the Tool House tab row does not grow the tab, until something
-builds them again. Folding a branch shut and opening it again is not a rebuild.</p>
+so the four routes below are what the tree and the tab row need; the Execution page's <strong>CWE</strong> canvas
+re-reads it the next time the selected step changes, while the Tool House canvas fixes the cutter's
+shape when its rendering connection is made and holds it until that connection is made again.
+Ticking it therefore changes nothing already built: the tree does not grow the nodes it gates, and
+the Tool House cutter's section-tab row does not grow the tab, until something builds them again.
+Folding a branch shut and opening it again is not a rebuild.</p>
 <p>Four things do rebuild one:</p>
 <ol>
 <li>Reload the browser. That rebuilds the whole application, every tree included.</li>
-<li>The project under the session changes — <strong>New</strong>, <strong>Load</strong>, <strong>Close Project</strong>, or a <strong>Save As</strong> to a
-location other than the one already open. Every screen the session has built is discarded and
+<li>The project under the session changes — <strong>New</strong>, a <strong>Load</strong> that picks a different project,
+<strong>Close Project</strong>, or a <strong>Save As</strong> to a location other than the one already open. Every screen the session has built is discarded and
 built again, and <strong>ReLoad</strong> does the same on the path already open.</li>
 <li>On Tool House, select a different tool in the left column and come back. The tab row is built for
 whichever tool is being shown, so moving between two tools rebuilds it twice.</li>