Hallo,
I just started using SBFspot v3.1.1.
Unfortunately, when getting the system data from pvoutput.org,
batch_datelimit and batch_statuslimit get overwritten with the already stored values,
i.e. the values obtained from pvoutput.org are ignored :-(
The following fixed it for me.
Axel.
```
--- sbfspot.3-original/SBFspotUploadCommon/CommonServiceCode.cpp 2015-09-08 21:55:20.000000000 +0200
+++ sbfspot.3/SBFspotUploadCommon/CommonServiceCode.cpp 2015-09-15 21:39:46.238899700 +0200
@@ -67,8 +67,8 @@
{
batch_datelimit = PVO.batch_datelimit();
batch_statuslimit = PVO.batch_statuslimit();
- db.get_config(SQL_BATCH_DATELIMIT, batch_datelimit);
- db.get_config(SQL_BATCH_STATUSLIMIT, batch_statuslimit);
+ //db.get_config(SQL_BATCH_DATELIMIT, batch_datelimit);
+ //db.get_config(SQL_BATCH_STATUSLIMIT, batch_statuslimit);
nextStatusCheck = now + timeBetweenChecks;
db.set_config(SQL_BATCH_DATELIMIT, db.intToString(batch_datelimit));
```
Comments: Fixed in V3.1.2
I just started using SBFspot v3.1.1.
Unfortunately, when getting the system data from pvoutput.org,
batch_datelimit and batch_statuslimit get overwritten with the already stored values,
i.e. the values obtained from pvoutput.org are ignored :-(
The following fixed it for me.
Axel.
```
--- sbfspot.3-original/SBFspotUploadCommon/CommonServiceCode.cpp 2015-09-08 21:55:20.000000000 +0200
+++ sbfspot.3/SBFspotUploadCommon/CommonServiceCode.cpp 2015-09-15 21:39:46.238899700 +0200
@@ -67,8 +67,8 @@
{
batch_datelimit = PVO.batch_datelimit();
batch_statuslimit = PVO.batch_statuslimit();
- db.get_config(SQL_BATCH_DATELIMIT, batch_datelimit);
- db.get_config(SQL_BATCH_STATUSLIMIT, batch_statuslimit);
+ //db.get_config(SQL_BATCH_DATELIMIT, batch_datelimit);
+ //db.get_config(SQL_BATCH_STATUSLIMIT, batch_statuslimit);
nextStatusCheck = now + timeBetweenChecks;
db.set_config(SQL_BATCH_DATELIMIT, db.intToString(batch_datelimit));
```
Comments: Fixed in V3.1.2