source: branches/r9/apps/rerun.cmd @ 5106

Last change on this file since 5106 was 1159, checked in by dkearney, 16 years ago

updated driver to allow the user to revisualize old run files just as rerun did. if driver can find the tool.xml file and where the application is installed, it can also allow the user to run new simulations after preloading old simulations.

Finally figured out where the current tags in group objects were coming from. controlOwner was adjusted to stop putting current tags in things. this only seemed to happen when the application also contained a loader, because we were doing an xml copy of nodes.

rewrote rerun to be a small wrapper around the "driver -load" command. rerun is now a script like rappture, it is populated with rappture's install directory from configure, so configure.in was updated. added some stuff for finding mcc in the configure.in script for a future commit

changed Rappture::Analyzer to accept -notebookpage configure flag so we can specify which page of the analyzer notebook should be currently showing. also inside of the analyzer, changed behavior of simstatus to allow us to still show a message even if the simulation button is disabled. this is helpful because we can tell the user why the simulation button is grayed out. one example of this is the case when we load old run.xml files, but cannot find a tool.xml file. the user cannot run a simulation, even if they change an input, because we can't figure out where the app is installed. now we can tell the user, why they cannot run the simulation.

File size: 286 bytes
Line 
1@REM %~dp0     = extract directory and path of argument 0 (command executed)
2@REM %M:~1,-1  = extract every between first and last charcter (the quotes)
3@REM These constructs require extended command options (Windows 2000 or later)
4@set M="%~dp0"
5@wish %M:~1,-1%driver -load %*
6
Note: See TracBrowser for help on using the repository browser.