#6 Simulation Console Box

[Benjamin Sprague]

A simulation log box should be created to show the
output stream from a simulation - this would help the
user detect a problem with the setup of the simulation.

The log should be saved with the run, so that if the
run "Finishes" when it shouldn't, the user can still
look at the output to try and diagnose why the
simulation program thought that it was done.

Could do this as follows:
* Automatically log the output to a file in the
"output" directory of the run.
* Create a file trace widget that will display this log
file and update whenever it changes.
* Put a button for a dialog with this in the "SimBox"
for the simulation.
* Put a page in the RunEditor with this widget in it.

[Benjamin Sprague]

Logged In: YES
user_id=1312775

If I'm going to do this I'll have to somehow get the
"stderr" output as well (since that's more important anyhow).

When getting stderr to copy right, make sure to not mess up
the "verification" code that checks to make sure that the
program executed is in fact Impact and has started
correctly. Also make sure to add the lines that this
verification code eats into the console box with everything
else.

[Benjamin Sprague]

Logged In: YES
user_id=1312775

Made a cheap version of this to hold us over until after 1.0
- It pops up a new window and can display the run as it
goes. However:

* It does not save the log in any file.
* It is re-started for each simulation of a particular run.
(So old data is not saved).
* It is not linked with the run editor dialog.
* It cannot be opened when the run does not have a simbox
showing.
* It does not open by default. But it does open
automatically if the simulation never reached the total
number of time steps. This way the user can see that it has
in fact crashed, and maybe the ImpactT output will be helpful.