Plan document export success messages
This commit is contained in:
@@ -649,6 +649,10 @@ Known local toolchain state:
|
||||
for image file exports, layer/frame collection directories, picked-directory
|
||||
stems, and MP4 suggested names as JSON and is covered for file, collection,
|
||||
and suggested-name states.
|
||||
- `pano_cli plan-export-message` exposes `pp_app_core` export completion
|
||||
dialog metadata for equirectangular image, layer/frame collection,
|
||||
depth/cube, animation MP4, and timelapse success paths as JSON, including
|
||||
platform-style destinations and suppressed/no-message paths.
|
||||
- `pano_cli plan-export-start` exposes `pp_app_core` export availability
|
||||
planning for license-gated, demo-blocked, and missing-canvas states as JSON;
|
||||
the live image, layer, animation-frame, depth, and cube-face export dialogs
|
||||
|
||||
File diff suppressed because one or more lines are too long
@@ -519,6 +519,10 @@ stems, and MP4 suggested names used by the live export dialogs.
|
||||
used by live image, layer, animation-frame, depth, and cube-face export dialogs
|
||||
plus MP4 animation and timelapse export dialogs before they call legacy
|
||||
canvas/recording export execution.
|
||||
`pano_cli plan-export-message` exposes the app-core export completion dialog
|
||||
metadata now consumed by the live legacy export bridge for equirectangular,
|
||||
layer/frame, depth/cube, animation MP4, and timelapse success reporting,
|
||||
including platform-style destinations and no-message/suppressed branches.
|
||||
`pano_cli plan-recording-session` exposes the app-core recording start, stop,
|
||||
clear, platform recorded-file cleanup, frame reset, and export progress-total
|
||||
decisions used by the live recording controls. Recording lifecycle and MP4
|
||||
@@ -655,6 +659,9 @@ choices, including image, layer, cube-face, depth, animation-frame, MP4, and
|
||||
timelapse dialog routing plus license/canvas gating. Export menu commands now
|
||||
dispatch through `DocumentExportMenuServices` in the shared app-shell bridge
|
||||
before legacy export dialogs and renderer/video execution continue.
|
||||
Export success-message metadata now also comes from `pp_app_core` through
|
||||
`pano_cli plan-export-message` and the legacy document-export bridge, reducing
|
||||
the bridge to export execution, platform handoff, and retained threading.
|
||||
`pano_cli plan-grid-operation` exposes app-core planning for grid heightmap
|
||||
pick/load/reload/clear, lightmap render capability/limit checks, and heightmap
|
||||
commit used by the live grid panel. Grid execution now dispatches through
|
||||
|
||||
Reference in New Issue
Block a user