Posted 17 September 2020, 6:13 pm EST
I have a typed list as a data source - can anyone help me understand the following inconsistencies:
- When is use the C1ExpressionEditor visually it recognizes all the property descriptor fields without issue using:
- Direct properties work using the property name
- Child properties work using the property name - you do not have to qualify the path (ie.ChildClassName.PropertyName)
- Custom Properties added with delegates work using the added property name
- When using the C1CalcEngine against this source:
- Direct properties work using the property name
- Child properties do not work using the property name - you have to qualify the path (ie.ChildClassName.PropertyName))
- Custom Properties added with delegates are note recognized
- When I replace the C1CalcEngine object with a C1ExpressionEditor and use it in code (it is not displayed) – I run into the same issues as (2) above using the C1CalcEngine.
I am trying to add a custom field to my typed list which assigns a delegate to a function that uses the C1CalcEngine to evaluate the formula entered by the user. It works with the restrictions shown in bullet 2 above.
Is there a way to have the C1CalEngine work with field names in the same way the C1ExpressionEditor does when displayed?
Why does C1ExpressionEditor evaluate fields differently when displayed vs using it in code without displaying it.