Are there any drawbacks to using the property()
expression function? I just want to make sure I’m not errantly creating a bunch of performance issues that I’ll need to correct down the road (à la tag()
).
Does property()
expression function even exists?
Yup, it’s a Perspective only expression function: property - Ignition User Manual 8.1 - Ignition Documentation
The only drawback I can think of is that it isn't possible to make it bidirectional using the expression function, but I don't know why it isn't possible to make property bindings work in the same way as tag bindings:
oh ok, haven’t used it yet. I don’t know
I’m interested in this as well. I presume though that it wouldn’t be nearly be as bad as using the tag() function. Although I still maintain that I’ve never actually had any issues with using that previously in Vision, despite avoiding using it now
1 Like