When you shift to a new screen, the new screen must be set up. To do this, the different controls are checked in the order they appear in the .vcd file. COMMAND and TOOL controls are executed immediately, and never again referenced. WIPTOOL controls are executed, but the output they generate fills itself in only over the course of a simulation.
NOTETo change the order of Control in the Venapp Editor use the View>Screen Definition command or Right-Click on an empty portion of the current screen.
Other controls are read and converted for display appropriate to the current conditions. For example, the WBVAR control reads the current workbench variable name, and stores it for display when painting. Input and BUTTON controls create windows, and prepare those windows so they contain the proper information.
Normally the controls are all processed then Vensim paints the window and waits for user input. This will not be the case if there is a COMMAND control calling for a simulation. In this case, the simulation is performed before any more controls are read. Because of this, COMMAND controls calling for a simulation should always appear last (or second last if there is a CLOSESCREEN control). Any controls appearing after a COMMAND control that calls for a simulation will give unpredictable results — and may display the wrong information. The only exception to this are additional COMMAND controls that can be used to reset the simulation configuration with commands such as SIMULATE>PAYOFF|.
