Trim main task queue, recording label, and canvas draw callbacks
This commit is contained in:
@@ -117,9 +117,10 @@ Current architecture mismatches that must be treated as real blockers:
|
||||
checkerboard background setup now route through retained draw-merge helpers,
|
||||
with the cache-to-screen checkerboard-plane callback setup also reduced and
|
||||
the merged-path checkerboard background-plane callback plus per-plane
|
||||
merged-texture draw callback plus the smoothing-mask face shader/draw pass
|
||||
plus heightmap, current-mode, and grid-mode callback setup now routed
|
||||
through the same retained helper family.
|
||||
merged-texture draw callback plus non-`draw_merged` per-frame layer draw
|
||||
callback plus the smoothing-mask face shader/draw pass plus heightmap,
|
||||
current-mode, and grid-mode callback setup now routed through the same
|
||||
retained helper family.
|
||||
- `app_layout.cpp` and `app_dialogs.cpp` are still mixed shell/controller files
|
||||
rather than thin composition/binding surfaces.
|
||||
- `App`, `Canvas`, `Node`, retained workers, and platform entrypoints still use
|
||||
@@ -137,13 +138,17 @@ Current architecture mismatches that must be treated as real blockers:
|
||||
retained local state object instead of separate process-wide globals, the
|
||||
Win32 async GL/context lock state now lives under
|
||||
`src/platform_windows/windows_platform_services.cpp` instead of `main.cpp`
|
||||
retained state, the canvas async worker now sits behind a named retained
|
||||
retained state, the main-thread queued task state now sits behind a narrow
|
||||
retained helper instead of `RetainedState.main_tasklist` /
|
||||
`main_task_mutex`, the canvas async worker now sits behind a named retained
|
||||
local worker-state helper instead of a bare static accessor, the
|
||||
prepared-file worker and the canvas async import/export/save/open worker now
|
||||
live under `AppRuntime` instead of retained static app-events/canvas
|
||||
workers, and `App::rec_loop()` now delegates worker-iteration orchestration
|
||||
into the retained recording bridge even though that retained recording path
|
||||
still owns the worker-side readback flow.
|
||||
workers, `App::rec_loop()` now delegates worker-iteration orchestration into
|
||||
the retained recording bridge, and `App::update_rec_frames()` now delegates
|
||||
recording label refresh through that same retained recording path even though
|
||||
the bridge still owns worker-side readback flow and encoder-state label
|
||||
reads.
|
||||
- Modern C++23 usage exists in extracted components, especially `std::span`,
|
||||
explicit result/status objects, and a few concepts, but the live app still
|
||||
does not consistently express ownership, thread affinity, or renderer
|
||||
|
||||
Reference in New Issue
Block a user