I haven’t changed the client poll rate, but these are UDTs. So it sounds like I’ll have to live with the lag since I can’t avoid the use of UDTs. Can you suggest any possible ways to make the transition look a little more appealing? The only thing I can think of is to bind to expressions that use “if” statements, displaying a blank whenever the value is -1. This seems to work, but will take a while to implement, and it’s going to be difficult to explain to the customer why I had to add so much complexity.
Another option would be to “pre-load” each of the UDTs in some sort of dataset, or by creating custom UDT properties and binding to each of my UDTs. I think I have plenty of horsepower for this, but there are two problems with these options.
- I have no idea how to get my UDT structure into a dataset. Is there some way beyond brute force scripting?
- If I create custom properties for each tag, I can’t figure out how to bind to one of the sub-elements because I can’t nest custom properties in an expression.