Yes, I can see that the new structure could need an enhanced write that takes the dtAlarmPeriod_t but I am not sure how it would actually be used.Can you explain the use case for changing the tick handler callback?And also can you explain the use case where the period type would be changed?
if (day==0) Alarm.alarmRepeat(H,M,S,handler);else Alarm.alarmRepeat(day,H,M,S,handler);
What I guess I'm asking is not to lose any of the features that have come about because someone needed them
I think simplicity is more important than rich functionality
time_t TimeAlarmsClass::read(AlarmID_t ID)
Going a bit further I have an issue with the Code: [Select]time_t TimeAlarmsClass::read(AlarmID_t ID) the fact that is returns 01 when failing is a bit strange because if someone set and alarm to 1 seconde after mignight it wont be able to distinguish an error from a real alarm.
Regarding complexity, I can't disagree, but it would be sad to lose working changes that other's might need and subsequently have to reinvent.
one more question so: could we then setup a daily midnight alarm (AFAIK time goes from 23:59:59 to 0:0:0)regardsViknet
Please enter a valid email to subscribe
We need to confirm your email address.
To complete the subscription, please click the link in the
email we just sent you.
Thank you for subscribing!
via Egeo 16