I suppose Time_t is used to roll over from hour 0 minute 59 to hour 1 minute 00? If i use the function presented above this isn't the case, it just counts up like an int..
DionSoepboer:
I suppose Time_t is used to roll over from hour 0 minute 59 to hour 1 minute 00? If i use the function presented above this isn't the case, it just counts up like an int..
I am not sure what you trying to say.
A time_t value is simply an incrementing value of seconds since the epoch, Different systems use different epochs, but the most common one in use came from Unix which is Jan 1, 1970 GMT.
In terms of adjustTime(), I have described in grueling detail, how adjustTime() works, and it is limitations as you have likely seen in the links referenced above.
Unless the Time library code is modified to use the value passed in as an offset that is always added to the actual time_t value. it cannot be used with a syncprovider.
But even then, in most cases, attempts to modify the time_t value are incorrectly trying to solve a timezone offset issue that should be solved some other way.
i.e. the time_t value should not be modified for the local timezone. That isn't how time is tracked when using epoch based time.
Maybe you could describe what you are really wanting to do, and why you need or are wanting to use adjustTime().