That is correct balala.

In order to use that Format as a formula, you would need something like:

Code: Select all

```
[MeasureTime]
Measure=Time
Format=%H+%M+%S
IfCondition=[MeasureTime]=37
IfTrueAction=[!Log "true"]
DynamicVariables=1
```

At 07:02:28 the

**number** value of the measure would not be 37, but would be 7, or just the hours. It will stop trying to evaluate it as a number as soon as it hits something non-numeric, like

**+**. If you use MeasureTime in a Formula or IfCondition, it will use the number value.

*The Format option of a Time measure does not in and of itself evaluate formulas. It simply takes what is returned and creates 1) A literal string value, and 2) a number value. (or a Timestamp). It takes what is literally returned and creates a number value until it hits something that isn't a number. Only digits, . (decimal point), and ***leading** + - (positive and negative, not addition and subtraction) are valid parts of a "number".
The

**string** value of the measure would be 7+02+28, and

**that** could be used elsewhere as a formula if you evaluate the string rather than the number value by using it as a [SectionVariable] and setting DynamicVariables=1. Way more trouble than it is worth in most cases I suspect.

The string 7+02+28 numerically evaluates to 37 in a formula with the small overhead of DynamicVariables, but setting Format=%H%M%S, the pattern "070228" evaluates to the number 070228 or 70228 just fine in an IfCondition without it.

Code: Select all

```
[MeasureTime]
Measure=Time
Format=%H%M%S
IfCondition=MeasureTime=70228
IfTrueAction=[!Log "true"]
```

While you could use the string value as a formula if you really want, I'm not sure I see a case where that makes sense, given the nature of clock arithmetic, which is modular in nature and not base-10. There might be some value in flattening it out as ((hours * 3600)+(minutes * 60)+(seconds)) I guess, but even then I'm not sure how.