Changeset 4740 in ntrip for trunk/BNC/src/bnchelp.html

Timestamp:

Sep 13, 2012, 10:53:34 AM (12 years ago)

Author:

weber

Message:

Documentation completed

File:

• trunk/BNC/src/bnchelp.html (modified) (2 diffs)

trunk/BNC/src/bnchelp.html

@@ -190 +190 @@
 </p>
 
-<p><img src="IMG/screenshot31.png"/></p>
-<p><u>Figure 6:</u> Management of configuration options in BNC.</p>
-
 <p>
 BNC maintains configuration options at three different levels:
@@ -199 +196 @@
 <ol type=b>
 <li>GUI, input fields level</li>
-<li>Working memory level</li>
+<li>Active configuration level</li>
 <li>Configuration file, disk level</li>
 </ol>
-<p>
-Configuration options are usually specified using GUI input fields (1) after launching BNC. When hitting the 'Start' button, configuration options are transferred one level down to BNC's working memory (2) allowing the program to beginn its operation. Pushing the 'Stop' button ends data processing so that the user can finally terminate BNC through 'File'->'Quit'->'Save Options' which saves processing options in a configuration file to disk (3). It is important to understand that:
-<ul>
-<li>Data processing in BNC generally uses configuration options from the working memory (2).</li>
+
+<p><img src="IMG/screenshot31.png"/></p>
+<p><u>Figure 6:</u> Management of configuration options in BNC:<br>
+&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Left: BNC in graphics mode where active configuration options are introduced through GUI input fields and finally saved on disk.<br>
+&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Middle: BNC in 'no window' mode where active configuration options are read from disk.<br>
+&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Right: BNC in 'no window' mode without configuration file where default configuration options are to be overwritten via command line options.</p>
+
+<p>
+Configuration options are usually specified using GUI input fields (1) after launching BNC. When hitting the 'Start' button, configuration options are transferred one level down to becomes BNC's active configuration (2) allowing the program to beginn its operation. Pushing the 'Stop' button ends data processing so that the user can finally terminate BNC through 'File'->'Quit'->'Save Options' which saves processing options in a configuration file to disk (3). It is important to understand that:
+<ul>
+<li>Active configuration options (2) are independant from GUI input fields and configuration file contents.</li>
 <li>Hence changing configuration options at GUI level (1) while BNC is already processing data does not influence a running job.</li>
-<li>Editing configuration options at disk level (3) while BNC is already processing data does also not influence a running job. However, there are two exceptions which enforce BNC to update certain options on-the-fly:</li>
+<li>Editing configuration options at disk level (3) while BNC is already processing data does also not influence a running job. However, there are two exceptions which force BNC to update certain active options on-the-fly:</li>
 <ul>
 <li>Pushing the 'Save & Reread Configuration' button lets BNC immediately reread its configuration from disk.</li>
 <li>Specifying the 'Reread configuration' option lets BNC reread its configuration from disk at pre-defined intervals.</li>
 </ul>
-<li>A certain BNC configuration can be started in 'no window' mode from scratch without any configuration file at all if configuration options for the working memory (2) are provided via command line.</li>
+<li>A certain BNC configuration can be started in 'no window' mode from scratch without any configuration file if options for the active configuration level (2) are provided via command line.</li>
 </ul>
 </p>