Enterprise Client Community

We have a fixgrid with editable fields and set avoidroundtrips=true.
We want a fast typing user to be able to enter all cells in several rows without interruption. A roundtrip when changing the row will always risk losing some input, let alone interfere with focus.

It looks like the flag "avoidroundtrips" is not obeyed when a change has been made in the current row.

So we would like to have an option like avoidroundtrips="really".
regards
Manfred

b.t.w. there also seems to be a flaw in that client events come in unexpected sequence. Change the value of a field and (without tab) click into the field of a different row. This change of row does not trigger a server roundtrip since the "row-is-changed"-Event from the field comes after the fixgrid has processed the newly selected row. But then any next click in the list triggers the roundtrip even if no further input has been done, so the server roundtrip also comes somehow unpredictable.

...yes, the purpose of "avoidroundtrip" is exactly as you describe it. Keep quiet if data is changed inside one row, but go to server when the user changes the row and has changed data.

To extends this to "always keep quiet" is not a big problem. We can do this near-term.

Björn

...the "b.t.w." issue you mentioned is solved with the next update... THanks!
Björn

Hi,

next update will contain the following improvements. Instead of true/false with AVOIDROUNDTRIPS you can define:

0 - always do rountrip on selection
1 - only rountrip on selection if changed data
2 - never do roundtrip on selection
true/false will still be valid of course, false being the new "0", true being the new "1"

Björn