@Bernhard, that's definitely the bug. We check for <...> later, but if the NumericEvaluator has already turned it into 0 then we'll think the user set it to 0.
@Bernhard, that's definitely the bug. We check for <...> later, but if the NumericEvaluator has already turned it into 0 then we'll think the user set it to 0.