Reuse existing scene projections when inserting ordinary canvas nodes
This commit is contained in:
@@ -670,3 +670,27 @@ Byte I/O/capacity/integrity failures throw instead of becoming a terminal malfor
|
||||
record. In particular a document reader preserves its ordinal for retry; the
|
||||
engine pauses the import, retains its editable prefix, and resumes after the I/O
|
||||
recovers. Ordinary malformed JSON/UTF-8 still uses the existing record diagnostics.
|
||||
|
||||
|
||||
Ordinary node insertion now keeps existing node/edge projections and transforms.
|
||||
A continuous change hint records element IDs rather than treating every element
|
||||
creation as a canvas topology change. A new visible known node uses the shared
|
||||
single-node builder; ordered member IDs restore the original depth-first canvas
|
||||
order. Hidden additions update the document without rebuilding visible objects.
|
||||
The layout index is rebuilt when visible node membership changes, so subsequent
|
||||
field edits address the new indices. Canvas changes, removal, reparenting,
|
||||
connection insertion/endpoints and unsupported placeholders retain full traversal.
|
||||
|
||||
This reduces projection construction, not the whole path to O(k). Reordering
|
||||
node references and rebuilding layout indices still takes linear work; missing
|
||||
membership services require a record scan. The 1000-node insertion test resolves
|
||||
only the new renderer, keeps all 1000 prior node objects and forbids full document
|
||||
record enumeration when a membership index is available. Actual toolbar insertion
|
||||
and ACK are checked separately in the page integration harness.
|
||||
|
||||
A local Chrome157/Next-development 1000-child copy probe completed with a first
|
||||
presented frame around 348 ms and frame-gap P95 around 33 ms. These observations
|
||||
are not an SLA or proof of overall speedup. The 10000-child baseline probe at
|
||||
0ce3abb remained unresponsive with a CPU-active renderer and approximately
|
||||
4.4 GiB sampled physical footprint, and was interrupted. Its completion, first
|
||||
frame and root cause remain unverified; 10000-node support is not claimed.
|
||||
|
||||
Reference in New Issue
Block a user