The play-test loads the game shell, which frees the screen the editor was
opened from (the novel_editor hub). Both the scenario's end and Stop used to
switch to the engine's main menu; the editor now remembers the route it left
and switches back to it, falling back to the main menu only when it was not
opened from a route. The tools_hub run of the windows suite plays its own
scenario and checks both ways back.
- test_suites/windows (--itest=tools_windows [--shots=<dir>]) opens every
tool window, fails on any engine error logged meanwhile, drives the
map/interactive/light canvases and can save a screenshot per window.
- The tools need the engine mods only; visual_novel_core is no longer a
dependency (the Novel Editor collection brings the content).
cthangover