Custom Query (104 matches)
Results (28 - 30 of 104)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#37 | fixed | bnc --version | ||
Description |
suggestion: bnc --version could output the bnc version. |
|||
#38 | fixed | bnc --key onTheFlyInterval "": seems to be ignored | ||
Description |
I'm trying to make the command line input override the configuration file with regard to the onTheFlyInterval setting. The config file has onTheFlyInterval=1 day while at the prompt I'm calling bnc -nw --key onTheFlyInterval "". I faced this problem using bnc to convert ntrip to rinex. Files were no longer being saved to disk after midnight UTC. I could get the intended behavior (files being saved uninterruptedly across day boundaries) changing the original setting onTheFlyInterval=1 day to onTheFlyInterval= in the config file. I could NOT get the intended behavior having onTheFlyInterval=1 day in the config file and bnc -nw --key onTheFlyInterval "" in the command line. It seems that the empty value "" is being ignored by bnc or perhaps even discarded by the shell itself. |
|||
#39 | fixed | documentation of no-window mode | ||
Description |
The documentation refers to both single and double dash input, i.e., -nw and --nw, as in, e.g., p.24: ./bnc --nw and on p.80: bnc.exe -nw It'd be more consist to adopt a single usage. Secondly, it'd be nice to emphasize in section 3.19.1, "No Window Mode - optional", that --nw implies autoStart=1; currently this is only explicitely mentioned in section 3.3.4, "Auto Start - optional", which says: "See BNC's command line option -nw for an auto-start of BNC in 'no window' mode." |