Author: derek Date: Fri Sep 22 00:09:22 2006 New Revision: 115 Modified: sofaswitch/trunk/callflow/callflow.dxy sofaswitch/trunk/callflow/docs/executionflow.dxy Log: Fix docs so it compiles. Modified: sofaswitch/trunk/callflow/callflow.dxy ============================================================================== --- sofaswitch/trunk/callflow/callflow.dxy (original) +++ sofaswitch/trunk/callflow/callflow.dxy Fri Sep 22 00:09:22 2006 @@ -81,7 +81,7 @@ EXAMPLE_PATH = EXAMPLE_PATTERNS = EXAMPLE_RECURSIVE = NO -IMAGE_PATH = +IMAGE_PATH = src docs INPUT_FILTER = FILTER_PATTERNS = FILTER_SOURCE_FILES = NO Modified: sofaswitch/trunk/callflow/docs/executionflow.dxy ============================================================================== --- sofaswitch/trunk/callflow/docs/executionflow.dxy (original) +++ sofaswitch/trunk/callflow/docs/executionflow.dxy Fri Sep 22 00:09:22 2006 @@ -5,7 +5,7 @@ The flow of execution is to follow the graph on the screen. Thus, when given a graph like -\image html1 forloop.png +\image html forloop.png it will enter the forloop, and go around and around until the termination condition is met. @@ -15,7 +15,7 @@ or passes through an Eventer type structure and goes nowhere. Consider the following graph -\image html2 simpleevent.png +\image html simpleevent.png Execution starts at the top, moves to the next node which sends off a request to obtain a new worker node. Then, the eventer box is entered, where we