Roberto, I don't know exactly what the "problem" is here, which behavior do you not like?
The meaning of "schedule_after" is "schedule at X past the current time." The meaning of "scheudle_at" is "schedule at the moment the system clock says X." These methods are behaving correctly. Eddie Roberto Riggio wrote: > Hi, > > the problem is the following: if I use the schedule_at function > in order to reschedule a timer I get the timer scheduled several > times if i move the system clock forward. > > On the other hand if I use the schedule_after function this > does not occur and the timer is scheduled only one even if I move > the clock several years in the future. > > The problem is annoying because I'm using click over an embedded > platform that forget the system date at each reboot (the default date > is Jan 2000). > _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
