gharris999;374875 Wrote: > What's the DST change mnemonic in French? Hum. I Don't know of a mnemonic. We call the summer and winter periods "heures d'été" (summer) and "heures d'hiver" (winter); So I guess it's clear enough the direction in which the clock goes. We're very clever, you know ;)
I wrote a long response, then scratched it off to say this: unless getNextAlarm guarantees to respond an epoch date (ie an absolute UTC date) that is: 1) picked among all known players *at the time of the query*, regardless of their current status 2) valid for the selected player be it on SC or SN at the time *of the alarm* then I think we're in the mud. (endless clash of policies, complex code, heavy maintenance, unhappy users) For me, a clear indication, is if the routine also reports on players connected to SN at the time of the query. If it doesn't, then I feel the contract is too weak. SN does/will muck with alarms and SC being asleep couldn't do anything to avoid failure. If it does, there's a good chance you shouldn't have to care at all about DST changes. (In any case, DateTime I used in my code has an isDST method you can call on a date object. If you call it on the query and alarm dates and see it flipping 0/1 or 1/0, you can start the incantation of your liking... ) -- epoch1970 ------------------------------------------------------------------------ epoch1970's Profile: http://forums.slimdevices.com/member.php?userid=16711 View this thread: http://forums.slimdevices.com/showthread.php?t=48521
_______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
