Why ever use an expression transform instead of an expression binding?

Ignition
1

i get map and script transforms, those add new capacity

but why ever expression transform?

2

To combine an indirect tag binding with an expression. When you don't need the tag value itself for any other purpose.

(I pretty much never do this, as another use for the tag value is almost inevitable.)

5 Likes
3

Well one project I saw that they chained multiple expression transforms to do increasingly more operations on each’s output… :face_with_raised_eyebrow:

4

I would use my Integration Toolkit's alternate tranform() for this--less overhead.

2 Likes
5

Definitely! From memory they were really simple though, things you could just do easily in a single expression. Don't know why they split it out

6

Expressions, by themselves, do not optimize common subexpressions or multiple references to the same tag/property. Perspective transforms and my transform() provide the opportunity for user-directed optimization. (Particulary helpful when using my iteration functions to move such outside the loop.)

7

They were using them like this:
Property Binding →
Expression Binding: if({value}, “StyleClass1”, “StyleClass2”) →

Expression Binding: {value} + “ StyleClass3” →

Expression Binding: {value} + “ StyleClass4”

I use your transform function all the time though :slight_smile:, very useful!

1 Like