Quantcast
Viewing all articles
Browse latest Browse all 47296

Why does TimePicker have old/lag context data during change event?

I'm trying to set readable tokens based on TimePicker entries but the token content retrieved and processed always seems to lag by one user input. Any suggestions/workarounds would be appreciated. Below is an example SimpleXML to reproduce the problem followed by example input/output:
0strftime(relative_time(now(),'timerange.earliest'), "%m/%d/%Y %H:%M:%S")strftime(relative_time(now(),'timerange.latest'), "%m/%d/%Y %H:%M:%S")

Earliest: $et$

Latest: $lt$

**Input 1:** 7 Days Ago **Output 1: (Default is All Time)** Earliest: 12/31/1969 16:00:00 Latest: 04/15/2016 16:46:13 **Input 2:** 4 Hours Ago **Output 2: (Result of previous selection of 7 Days Ago, not 4 hours Ago)** Earliest: 04/08/2016 16:00:00 Latest: 04/15/2016 16:48:33 **Input 3:** 30 Days Ago **Output 3: (Result of previous selection of 4 Hours Ago, not 30 Days Ago** Earliest: 04/15/2016 12:50:00 Latest: 04/15/2016 16:50:15

Viewing all articles
Browse latest Browse all 47296

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>