Hi Terry,
It could be a delay on when Grabber actually gets the new data and is able to displays it... i.e.
The TimeStamp I show is the time that the RealTime.txt file has been given from Cumulus
as it is generated (by Cumulus). There may be a lag or error when Grabber try's to get the Realtime.txt file
on it's 1st attempt, so it re-try's and then gets it on the next attempt.
The Graph will on the 1st attempt then display the last value it had i.e. the old Realtime.Txt data that is
still currently displayed in the TextBox, but give its own timestamp on the graph (as the graph gets the latest
system time and displays it on the the graph, which will then be out of sync with
the RealTime.txt TimeStamp), until the next successful grab of the Realtime.txt file is gotten, then
the TimeStamp will be updated and the graph will display the new value.
This could be why you are seeing a bit of a lag between the TimeStamp and the Graph.
Also, if the Cumulus RealTime.txt file is updated at a different time interval, i.e. longer than the Interval
set in Grabber, the times on the TimeStamp and the Graph will be out of sync.
Therefore with the above in mind, I think we will have to accept that there may be occurences when the
TimeStamps will be out of sync. If my program was actullay generating the Cumulus RealTime.txt file
and not reading it, I would be able to sync both the creating of the Realtime.Txt and update the
graph at the same time. But as my program only reads the Realtime.txt file, this is the best I can do
I hope the above makes sence LOL, I've just got back in from sitting in the garden after having a pint of
homebrew and am now very lathargic LOL
I am glad that the "CacheBuster" version has helped
, I will release this in the next version once I have
added another feature. (Thankyou
mcrossley for you input on adding a "CacheBuster", that seems
to have helped us out
)
Login 
Register
Enhancement requests
Search
