-All configuration files for running BNC on Unix/Linux/Mac systems are saved in directory ${HOME}/.config/BKG. The default configuration file name there is 'BKG_NTRIP_Client' with suffix '.conf'. -
--On Windows systems all configurations for running BNC are saved in register HKEY_CURRENT_USER/Software/BKG. The default configuration register name there is 'BKG_NTRIP_Client. -
--The default 'BKG_NTRIP_Client' can be changed. The contents of configuration files/registers can easily be edited. Some options can be changed on-the-fly. See annexed 'Configuration Example' for a complete set of saved configuration options. +As a default, configuration files for running BNC on Unix/Linux/Mac systems are saved in directory '${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'. The default configuration file name is 'BNC.ini'.
++The default file name 'BNC.ini' can be changed and the file contents can easily be edited. On graphic systems it is possible to Drag & Drop a configuration file icon to start BNC. Some configuration options can be changed on-the-fly. See annexed 'Configuration Example' for a complete set of configuration options.
@@ -159,8 +155,6 @@ Use smaller font size if the BNC main window exceeds the size of your screen. -
3.4.3 Reread Configuration - optional
-When operating BNC online in 'no window' mode (command line option -nw), some configuration options can nevertheless be changed on-the-fly without interrupting the running process. For that you force the program to reread parts of its configuration in pre-defined intervals from the disk. Select '1 min', '1 hour', or '1 day' to let BNC reread on-the-fly changeable configuration options every full minute, hour, or day. This lets in between edited options become effective without interrupting uninvolved threads. See annexed section 'Configuration Example' for a Unix/Linux/Mac configuration file example and a list of on-the-fly changeable options. +When operating BNC online in 'no window' mode (command line option -nw), some configuration options can nevertheless be changed on-the-fly without interrupting the running process. For that you force the program to reread parts of its configuration in pre-defined intervals from the disk. Select '1 min', '1 hour', or '1 day' to let BNC reread on-the-fly changeable configuration options every full minute, hour, or day. This lets in between edited options become effective without interrupting uninvolved threads. See annexed section 'Configuration Example' for a configuration file example and a list of on-the-fly changeable options.
@@ -557,5 +551,5 @@-When selecting the serial communication options listed below, make sure that you pick those confiured to the serial connected device. +When selecting the serial communication options listed below, make sure that you pick those configured to the serial connected device.
@@ -838,5 +832,5 @@ Window mode: Hit 'Save & Activate Options' while BNC is in window mode and already processing data to let changes of your streams selection immediately become effective.-No window mode: When operating BNC online in 'no window' mode (command line option -nw), you force BNC to reread its 'mountPoints' configuration option from disk at pre-defined intervals. Select '1 min', '1 hour', or '1 day' as 'Reread configuration' option to reread the 'mountPoints' option every full minute, hour, or day. This lets a 'mountPoints' option edited in between in the configuration file or Windows register become effective without terminating uninvolved threads. See annexed section 'Configuration Example' for a Unix/Linux/Mac configuration file example and a list of other on-the-fly changeable options. +No window mode: When operating BNC online in 'no window' mode (command line option -nw), you force BNC to reread its 'mountPoints' configuration option from disk at pre-defined intervals. Select '1 min', '1 hour', or '1 day' as 'Reread configuration' option to reread the 'mountPoints' option every full minute, hour, or day. This lets a 'mountPoints' option edited in between in the configuration file become effective without terminating uninvolved threads. See annexed section 'Configuration Example' for a configuration file example and a list of other on-the-fly changeable options.
@@ -853,10 +847,10 @@-Command line options are available to run BNC in 'no window' mode or let it read data from a file in offline mode. BNC will then use processing options from the configuration file (Unix/Linux/Mac) or from the Windows register. Note that the self-explaining contents of the configuration file or the Windows register can easily be edited. It is possible to introduce a specific configuration file/register name instead of using the default name 'BKG_NTRIP_Client'. +Command line options are available to run BNC in 'no window' mode or let it read data from a file in offline mode. BNC will then use processing options from the configuration file. Note that the self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration file name instead of using the default name 'BNC.ini'.
3.15.1 No Window Mode - optional
-Apart from its regular windows mode, BNC can be started on all systems as a background/batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file/register on disk. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems. +Apart from its regular windows mode, BNC can be started on all systems as a background/batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file on disk. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems.
@@ -871,5 +865,5 @@
-Note that it is necessary to define a date and time for the first epoch because RTCM streams do not contain complete time stamps as needed for RINEX. Note further that when running BNC in offline mode, it will use options for file saving, interval, sampling etc. from its configuration file/register. +Note that it is necessary to define a date and time for the first epoch because RTCM streams do not contain complete time stamps as needed for RINEX. Note further that when running BNC in offline mode, it will use options for file saving, interval, sampling etc. from its configuration file.
3.15.3 Configuration File - optional
Example:
-./bnc --conf MyConfig
+./bnc --conf MyConfig.ini
-This leads to a BNC job using configuration file 'MyConfig.conf' or the Windows configuration register 'MyConfig'. +This leads to a BNC job using configuration file 'MyConfig.ini'. The configuration file will be saved in the current working directory.
@@ -981,5 +975,5 @@-The following is an example for the contents of a Unix/Linux/Mac configuration file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. It enables the retrieval of stream ACOR0 form www.euref-ip.net and FFMJ3 from www.igs-ip.net for the generation of 15 min RINEX files. RINEX files are uploaded to an archive using script 'up2archive' : +The following is an example for the contents of a configuration file 'BNC.ini'. It enables the retrieval of stream ACOR0 form www.euref-ip.net and FFMJ3 from www.igs-ip.net for the generation of 15 min RINEX files. RINEX files are uploaded to an archive using script 'up2archive' :
[General] @@ -1230,8 +1224,5 @@-Note that on Windows systems configuration options are saved in register BKG_NTRIP_Client. -
--Note further that the following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data: +Note that the following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data:
Index: trunk/BNC/bncwindow.cpp =================================================================== --- trunk/BNC/bncwindow.cpp (revision 1540) +++ trunk/BNC/bncwindow.cpp (revision 1541) @@ -89,7 +89,4 @@ _actSaveOpt = new QAction(tr("&Save && Activate Options"),this); connect(_actSaveOpt, SIGNAL(triggered()), SLOT(slotSaveOptions())); - - _actRemoveOpt = new QAction(tr("&Remove Options"),this); - connect(_actRemoveOpt, SIGNAL(triggered()), SLOT(slotRemoveOptions())); _actQuit = new QAction(tr("&Quit"),this); @@ -857,18 +854,4 @@ } -// Remove Options -//////////////////////////////////////////////////////////////////////////// -void bncWindow::slotRemoveOptions() { - - int iRet = QMessageBox::question(this, "Remove", "Remove" - " options from disk?", - QMessageBox::Yes, QMessageBox::No, - QMessageBox::NoButton); - if (iRet == QMessageBox::Yes) { - bncSettings settings; - settings.remove(""); - } -} - // Save Options //////////////////////////////////////////////////////////////////////////// @@ -1110,6 +1093,4 @@ _menuFile->addAction(_actSaveOpt); _menuFile->addSeparator(); - _menuFile->addAction(_actRemoveOpt); - _menuFile->addSeparator(); _menuFile->addAction(_actQuit); Index: trunk/BNC/bncwindow.h =================================================================== --- trunk/BNC/bncwindow.h (revision 1540) +++ trunk/BNC/bncwindow.h (revision 1541) @@ -68,5 +68,4 @@ void slotFontSel(); void slotSaveOptions(); - void slotRemoveOptions(); void slotAddMountPoints(); void slotGetData(); @@ -92,5 +91,4 @@ QAction* _actFontSel; QAction* _actSaveOpt; - QAction* _actRemoveOpt; QAction* _actQuit; QAction* _actGetData;