Presently, I have initialized an array with %CDATE %CTIME,%CODATE %COTIME. I then convert arr(1) and arr(2) from date-time to seconds. Somewhere in this an odd quirk emerges that sometimes does not convert correctly.
Rather than spending further time running it down, is there a way to just retrieve the epoch timestamps?
And if I may be so bold....
I am aware that Pent once declared that no new globals would be created unless there were no other means of derivation, but here implementation seems to have evolved cart-before-horse. Globals for month/year/hour/min/sec were not created because these elements can be derived by conversion and search/replace. Similarly, calendar test returns epoch seconds and a user must var-convert for date and time. But in the case of last ring/last dial, we have separate date and time globals that must be back-converted to epoch seconds for accurate comparison or evaluation. Though harmless, it's inconsistent.
I'm not necessarily suggesting re-writing Tasker, but as Tasker evolves in future releases, perhaps this is an inconsistency that merits revision. (In other words, deploying a %CITS, %COTS, %SMSRTS, and %ERTS containing epoch timestamp and de-listing %CTIME, %CDATE, %COTIME, %CODATE, %SMSRT, %SMSRD, %ETIME, and %EDATE in the var list so that they eventually fall out of use and can be deleted after two years or so.)
--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/2d720709-9846-43f3-b942-fb6fb2ba53ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.