Recent Posts21
Troubleshooting / Problem with now_time_datestr
« Last post by andyock on 15 Apr 2024, 17:41 »Hi. Not sure what I'm doing wrong here help would be appreciated.
I have a trigger which is checking in its condition the value of now_time_datestr against a user variable containing a previous assignation of said variable. basically I'm looking for a date change between the last market where the trigger was run and the current one.
I've attached the trigger and the log. The condition check is not working correctly because the previous value of the date stored in variable dateString is not being preserved as a string. The intermediate and final values are different namely:
My condition against this value with the current date is therefore always true which means I'm always detecting a date change.
Is this something I've done wrong ? I don't understand why the intermediate value is a string but the final value has changed to a floating point.
Trigger and log attached. Cheers in advance.
I have a trigger which is checking in its condition the value of now_time_datestr against a user variable containing a previous assignation of said variable. basically I'm looking for a date change between the last market where the trigger was run and the current one.
I've attached the trigger and the log. The condition check is not working correctly because the previous value of the date stored in variable dateString is not being preserved as a string. The intermediate and final values are different namely:
| Checking condition or Favourite's Trigger Expression dateString is not equal to now_time_datestr. | |
| 17:19:54 | Selection: Phoenix Passion, initial expr.: dateString, intermediate: 15/04/2024, final: 0.00185277. |
Is this something I've done wrong ? I don't understand why the intermediate value is a string but the final value has changed to a floating point.
Trigger and log attached. Cheers in advance.