On Aug 22, 3:26 pm, BossMan <
adam.marynow...@gmail.com> wrote:
> There is at least one thing you can do easier: replace Locale Execute with
> Secure Settings and read the %STDOUT (instead of a file).
I think I'll probably go for this one, since it's a bit more redirect
than back and forth with a file etc. Didn't realize it'd set %STDOUT,
good stuff.
> As for %TIMES - there are some options for time/date convertion in the
> Variable Convert action - haven't check them, but maybe one of them will
> suit your needs.
Yeah, not seeing anything there. I guess Pent agrees. Haven't tried
seconds to long date time, but unless %TIMES is epoch, that won't
help.
> If not, then you can try doing some manual calculations: add a periodic task
> that will be run, say every hour. In that task, store the current %TIMES
> value in a separate variable (e.g. $MY_TIMES). Then, in a task where you
> need the seconds, do (%TIMES - %MY_TIMES)/60, take the fractional part,
> multiply by 60 and you're done ;) BTW, this is just a wild guess, not tested
Yeah, I've done this before, and I really wanted to avoid it ;)
And THANKS Pent. Add a seconds variable somewhere :P