|
<br />DO! ..
<br />.:.1 L:?
<br />
<br />sel.f), 1120000 (dfsave.f), and 1130000 (dfdel.f). In this manner, a topological network or
<br />directed tree is maintained for all routines in the system.
<br />
<br />Each routine that handles user control, i.e. displays a menu and allows the user to select
<br />from the items, follows a similar structure. In the first section of a routine, the topological
<br />indexes are set, one for the current routines index, one for the parent (calling) routines in-
<br />dex, and one for the selected index. It is the selected index that gets affected when the
<br />user selects a given item. Next, the menu is drawn on the screen using various toolbox
<br />calls. Then, the routine CONTROL is called, which serves as a central routine to pass on
<br />the various mouse clicks. Here the mouses clicks (and even location) are checked in the
<br />routine TMYSELO.fto see what item should be highlighted by the location of the mouse.
<br />Next, a global boolean variable ESC is checked to see if it was set to true in CONTROL.
<br />If it was, then the user selected the ESCAPE button. In this case, the value of the selected
<br />topologic index is set to equal the parent topological index (the calling routine). The con-
<br />trol then passes the next section, this passed section being the area where, had an item on
<br />the current menu been selected, then the desired routine would have been called. The con-
<br />trol ends up in the final section which simply closes out of the routine.
<br />
<br />In the case where the user selects the top level control bar and chooses one of the four
<br />modules, the selected topological index, a global variable, gets set to the corresponding
<br />value. In the middle section of each routine, just after the boolean variable ESC is
<br />checked, is a check to see if the selected index is less than the current topological index.
<br />Because each menu routine where the user has a choice of selection calls a subsequent
<br />routine, routines get stacked up. Checking the global selected topological index against
<br />the current toplogical index allows multiple levels of routines to, in effect, back out of the
<br />calling or decision stack. This allows the user to be deep in a decision tree and then by
<br />choosing one of the four modules in the top control bar, jump to the top level of one of the
<br />four modules.
<br />
<br />1.7 Editable graphs and slider
<br />
<br />The editable graphs and slider functionalities are compilations of various toolbox routines,
<br />that is, they are not built from existing toolbox routines. In both cases, toolbox routines
<br />have been modified to provide the extra functionality.
<br />
<br />For the editable graphs, the routines TMYSELO, BOXRUB, RUBBAND, TGRUBBOX,
<br />DGillST, DGLINE, DGBAR, TSR4GR, TGSRCHB, and rGSRCHL are involved. The
<br />graphs are drawn on the screen by DGillST, DGLINE, and DGBAR, according to their
<br />graph type. These routines must also set up the arrays which store not only the x, y coor-
<br />dinates of the graph points, but also which trace (a time series line or bar) number corre-
<br />. sponds to the array script (which contains the basic information necessary to produce a
<br />graph) and in which graph a trace is located. These arrays are required because for a single
<br />line on the graph that represents an input parameter, there are two traces needed to draw the
<br />line. Thus, there is not a direct or even predictable correspondance between the script array
<br />and the traces on the scrren. These arrays are used in all of the above listed routines.
<br />
<br />24 Month Study Proiect DooJmentation Volume n
<br />
<br />618191
<br />
<br />7
<br />
|