User | Kudos |
---|---|
4 | |
4 | |
4 | |
2 | |
2 |
When sending data to an XControl terminal, the action returns immediately regardless of how long the XControl has to update its display. When using an XControl in a situation where the individual data updates are very close together, the "Data Change" Events within the XControl stack up and the XControl can lag significantly (Multiple seconds) behind the ACTUAL data.
Think of a typical In-box on an overworked clerk's desk. It just keeps getting higher and higher, and he's stuck dealing with "old" data.
When the loop calling the XControl is stopped, the XControl will continue updating even though it's not actually receiving any new data. It must still work through the backlog of old data..... This is extremely bad from a UI point of view.
This is different when using any of the in-built controls. If a control takes 5ms to update, the loop sending to the terminal for that control will wait until the control is finished displaying. As such, the control effectively limits the rate (5ms) of the calling loop to match its drawing speed.
XControls should do this also (perhaps automatically, perhaps optionally).
Discussed in forums HERE.
Shane.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any idea that has received less than 5 kudos within 5 years after posting will be automatically declined.