omar/panopainter
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Route canvas view execution through app core

Browse Source
This commit is contained in:
omigamedev
2026-06-05 05:47:42 +02:00
parent 9373e07d3e
commit e42afcc83f
15 changed files with 456 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/modernization/build-inventory.md
View File

@@ -226,9 +226,14 @@ Known local toolchain state:
`pp_app_core` contracts while legacy dialogs, pickers, cloud/share/export,
Tools, About, history, canvas-clear, settings, and platform SonarPen startup
execution remain tracked by `DEBT-0029`, `DEBT-0030`, `DEBT-0031`,
`DEBT-0033`, `DEBT-0034`, and `DEBT-0035`. `NodeCanvas::reset_camera()`
now consumes the tested `pp_app_core` reset-camera state exposed through
`pano_cli plan-canvas-camera-reset` before retained canvas camera mutation.
`DEBT-0033`, `DEBT-0034`, and `DEBT-0035`. `src/legacy_canvas_view_services.*`
is the shared bridge for reset-camera, viewport-density, and cursor-mode
execution; live Tools reset-camera, document open/new-document reset, cloud
download reset, and options viewport/cursor callbacks consume the tested
`pp_app_core` canvas-view plans exposed through
`pano_cli plan-canvas-camera-reset`, `pano_cli plan-canvas-view-density`,
and `pano_cli plan-canvas-view-cursor-mode` before retained canvas mutation
and settings writes.
- `src/legacy_app_preference_services.*` is the current app-shell bridge for
options-menu preference execution. It keeps UI scale, viewport scale, RTL,
VR mode, VR-controller, auto-timelapse, and canvas cursor-mode callbacks on