deploy.

App/wwwroot/HiAPI-docsite/manual/basics/the-app-window.html

@@ -92,7 +92,7 @@ along the bottom. The frame is built once and stays mounted for the whole sessio
 described here is present on every page. A project change is the one event that reaches into it and
 rebuilds what the middle holds.</p>
 <p>The whole frame at <code>/execution</code>, with the demo project open. Only the column quick-toggles and the
-connection badge, in the middle of the bar, are there because of the page underneath them — the logo,
+connection badge, in the right-hand group, are there because of the page underneath them — the logo,
 the three dropdowns, the page title and <strong>Show Log</strong> sit on the bar whatever page is open, and the
 sign-out button turns on whether a sign-in is asked for rather than on the page. The strip along the
 very bottom is the footer, reading <strong>Ready</strong> because nothing has been reported yet.</p>
@@ -111,12 +111,12 @@ column), three on General Setup. Each glyph is a small map of the page with its
 and each tooltip names the column it toggles. Tool House lays itself out with draggable splitters
 and gets no buttons here.</li>
 <li><strong>The connection badge</strong> — the Execution page only. See below.</li>
-<li><strong>The current page's title</strong> — the destination's own title, which is where two controls read
-differently from where they land: the Page menu's <strong>Legacy-Controller</strong> entry opens the page titled
-<strong>Controller</strong>, and <strong>Show Log</strong> opens the page titled <strong>Log Viewer</strong>.</li>
+<li><strong>The current page's title</strong> — the destination's own title, which is where one control reads
+differently from where it lands: <strong>Show Log</strong> opens the page titled <strong>Log Viewer</strong>.</li>
 <li><strong>Show Log</strong> — present on every page.</li>
 <li><strong>The sign-out button</strong> — labelled with the signed-in user name, or <strong>Logout</strong> when the service has
-no name for it. It is there only while the service asks for a sign-in.</li>
+no name for it. It is there only while the service asks for a sign-in and this browser has passed
+it.</li>
 </ul>
 <h2 id="the-page-area">The page area</h2>
 <p>Everything between the bars is the current page, and every page reached during a session stays built:
@@ -125,16 +125,22 @@ half-finished and an established rendering connection exactly as they were.</p>
 <p>Two things it does not carry over. Nothing restores a scroll position inside a panel: coming back to a
 page finds its panels scrolled to where a fresh mount would put them. And a browser reload is not a
 navigation — it rebuilds the whole application and empties the cache; what survives it is what lives
-outside the page area, namely the address (a <code>?tree=</code> selection in it included) and the layout the
-browser keeps for itself.</p>
+outside the page area: the address (a <code>?tree=</code> selection in it included), the layout the browser
+keeps for itself, and the preferences the service holds — the language, <strong>Show Physics Options</strong>, and
+which of the Execution page's charts, its <strong>Session Messages</strong> panel and its <strong>Step Properties</strong>
+panel are switched on.</p>
+<p>The column buttons are remembered per page — the two tree pages each keep their own choices — while
+the dock widths and the list of unfolded tree nodes are single settings both of them share, so
+widening the dock on Execution widens it on General Setup too.</p>
 <p><strong>F5 to F8 belong to the Execution page.</strong> They drive its transport — F5 starts or resumes, F6
 pauses, F7 runs one NC line, F8 runs one machining step — and they are bound only while that page is
 the one on screen, so on every other screen F5 is the browser's own reload. A key whose button is not
 available at that moment, or that is pressed with the focus in a text field, is handed back to the
 browser instead. That matters most for F5: while a run is in progress the start button is
-unavailable, so the key reloads the page and takes the session with it.</p>
+unavailable, so the key reloads the page and the screens the session had built go with it.</p>
 <h2 id="what-a-project-change-does">What a project change does</h2>
-<p><strong>New</strong>, <strong>Load</strong>, <strong>ReLoad</strong> and <strong>Close Project</strong> discard every page the session has built and
+<p><strong>New</strong>, a <strong>Load</strong> that picks a different project, <strong>ReLoad</strong>, a <strong>Save As</strong> to a location other
+than the one already open, and <strong>Close Project</strong> discard every page the session has built and
 rebuild it against whatever the project is afterwards — nothing at all, after <strong>Close Project</strong>.
 That is what stops a screen showing values from a project that is not open any more, and it is also
 why in-page state that was never saved does not survive one.</p>
@@ -158,16 +164,18 @@ the full text with whatever caption came with it. The icon in front decodes the
 information mark for a plain status line, a green tick for a success, an amber triangle for a warning,
 a red mark for a failure. The clock button beside it opens <strong>Recent messages</strong> — newest first, capped
 at a hundred, each row repeating its severity as a coloured strip down the left edge and carrying the
-time it arrived. That list belongs to this browser and this session: <strong>Clear</strong> empties it, a reload
-empties it, and it is written down nowhere.</p>
-<p><strong>Middle — the session strip.</strong> It is drawn only while a run has produced something, and the space is
-simply empty the rest of the time. A glyph leads each line — a locator mark on a cursor tick, the
+time it arrived. That list belongs to this browser and this session: <strong>Clear</strong> empties it and returns
+the line in front of it to <strong>Ready</strong>, a reload empties it, and it is written down nowhere.</p>
+<p><strong>Middle — the session strip.</strong> It is drawn only while a run has produced something, it is emptied by
+a project change, and the space is simply empty the rest of the time. A glyph leads each line — a locator mark on a cursor tick, the
 message's own severity mark otherwise — and an anchor follows it in a monospaced prefix wherever the
 entry carries one: a cursor line carries <code>Sn</code> and the sentence index it sits on, a message line the
-anchor the message itself supplies. Hovering opens the recent activity behind it; clicking pins that
-list open.</p>
-<p><strong>Right — the background zone.</strong> It appears only while a project file operation is in flight, names
-the operation and the path it is working on, and vanishes when the operation ends.</p>
+anchor the message itself supplies. Hovering opens the recent activity behind it — newest first,
+capped at thirty, with a run of consecutive cursor ticks collapsed into its latest; clicking pins
+that list open.</p>
+<p><strong>Right — the background zone.</strong> It appears only while one of the <strong>Project</strong> menu's operations is in
+flight — <strong>Close Project</strong> included — names the operation and the path it is working on, and vanishes
+when the operation ends.</p>
 <p>Switching the language re-resolves the interface at once and without navigating: the menus, the page
 title in the bar and the browser tab title all change. The two message regions do not follow. Each
 line in the recent list and in the session strip keeps the language it was raised in, so a footer read
@@ -188,9 +196,6 @@ healthy rather than every connection that exists.</p>
 explain and none appears. The tooltip lists one row per connection, <code>Rendering</code>, <code>Shell</code>, <code>NcDiag</code> and
 the rest, and those names are identifiers rather than interface text: in a translated session only the
 state beside each name changes language.</p>
-<p>The buttons that hide those panels' columns are remembered per page. The two tree pages each keep
-their own column choices, while the dock widths and the list of unfolded tree nodes are single
-settings both of them share — widening the dock on Execution widens it on General Setup too.</p>
 <h2 id="see-also">See Also</h2>
 <ul>
 <li><a href="index.html">Basics</a> — the rest of what is true on every screen</li>