Attempt #2; commit bbe8925378 was stupid and useless.
Scenario: run driver without any saved settings.
Before this commit (in driver repo), the driver would crash on quit.
Triggered by commit 62f8f2c498.
I'm not sure how to fix this, so I'm going to just document it in a
couple of places for now. I also had to perform some low-level surgery
going around the driver program.
This one is a bit of a mind-bending change.
Goal: I want the driver to refresh its command palette after creating a
new definition. Currently I can create a new definition and fail to see
it in the command palette.
Blocker: to do this I need to set Manifest_navigator.reload after
hitting F4. But the F4 handler is in the non-live substrate of the app,
and it shouldn't know about the code running live. Manifest_navigator is
entirely live.
Solution:
1. create and document a new event called on.code_submit (this change)
2. `git commit` the change in the driver repo
3. shut down the meta driver, `git pull upstream` and restart
4. Define on.code_submit in the meta driver to set
Manifest_navigator.reload, hit F4 to send it to the driver. At this
point it will cause the manifest to update any time I create new
definitions in the test app, but I rarely do that, so the effect
won't be very visible.
5. Shut down the meta driver, `git pull upstream` and restart
6. Now I can create new definitions in the driver using the meta
driver, and see them update the command palette in the meta driver.