Issue I357 [80,high,resolved] Prevent simion.command() calls from having side-effects such as leaving additional PAs around in memory and parameters modified. Reported by rbalthazor-20070124 and bud Description: In SIMION 8.0.x versions prior to 8.0.2, at the completion of in-process Lua calls to "simion.command(...)" commands, SIMION did not properly unload PAs created in memory. Commands could also affect and be affected by the current refine and fly parameters. This could result in memory exhaustion and hard to diagnose run-time side-effects between commands. However, equivalent commands executed from the command-line interface (e.g. "os.execute([['c:/program files/simion-8.0/simion.exe --nogui ...']])") are not affected since that creates a new, clean SIMION process for each command. Resolution: Starting in 8.0.2, all PAs created in memory by a "simion.command(...)" command are unloaded after the command finishes (i.e. no difference is seen in the PA list on the main screen before and after a command runs). Also, default command parameters are now localized to defaults, which means that omitted default parameters are not affected by the current values prior to running, nor do included parameters affect the current values after running. In short, side-effects are eliminated. One exception to this rule is the "fly" command, which will also entirely clear any non-empty PA list and particle definitions after (and before) running. This is designed to minimize side effects given technical limitations (that may be removed in the future), but it generally is not expected to present a problem. The "fly" command is currently prevently from executing in the View screen for this reason. Original report: http://www.simion.com/discuss/viewtopic?p=1273 Workaround in 8.0.1: (1) Invoke a new SIMION process for each command, e.g. os.execute([['c:/program files/simion-8.0/simion.exe --nogui ...']]) rather than an in-process simion.command("...") command. Affects: 8.0.0-8.0.1. Resolved in 8.0.2. Issue I357 [programming,med-high,resolved] run_stop() now disables window frame (prevents other user actions) and properly functions in non-GUI batch mode. Affects: 8.0.0-8.0.1. Resolved in 8.0.2.