26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
# Window command batch boundaries
|
|
|
|
Batch: `890fd2edecd5bf5d51905062`.
|
|
|
|
The existing native window branch now obtains live window state from the actual
|
|
QMdiArea. It previously called MainWindow C++ helpers through the Python Qt
|
|
wrapper after executing the command, risking a reporting exception after a
|
|
successful operation. MDI discovery now happens before command execution.
|
|
Desktop command execution remains owned by Gui.runCommand and CommandWindow.cpp,
|
|
including ordering, cascade layout, and close confirmation or veto behavior.
|
|
|
|
All four selected commands remain incomplete for the headless Web runtime:
|
|
Std_ActivateNextWindow, Std_ActivatePrevWindow, Std_CascadeWindows, and
|
|
Std_CloseActiveWindow. The current Web dispatcher routes them to
|
|
web.standardCommand, whose native window branch requires App.GuiUp. The supplied
|
|
mounted-shell anchors do not connect a browser window lifecycle to that branch.
|
|
Completing this requires the real mounted view inventory, activation and layout
|
|
owner, and close lifecycle with native document saving and close vetoes. Document
|
|
lists alone cannot substitute for windows, because multiple views and text
|
|
windows have distinct lifetimes. No fixed window state or registration markers
|
|
were added, and the GUI branch repair is not claimed as Web implementation.
|
|
|
|
No builds, tests, browser validation, benchmarks, acceptance, or historical
|
|
reconciliation were run. Incremental build, sync, and route receipts belong to
|
|
the outer pipeline and do not establish business acceptance.
|