Search found 232 matches

we did a new measure with/without sorters/filter for the single update of one change operation (as we did together):

no filter, sorter
44ms

filter, no sorter
109ms

these methods are not existing in the regular 5.5., right:

suspendChangeTracking
resumeChangeTracking

sorry you are right, we did not think of this global filter (don't care about the format, this is because we have all that configurable via object settings): "taskStoreFilters": { "filterBy": { "function": { "arguments": "object", "body": &...

in the test scenario that we went through on our server there was not any filtering active (assuming that filtering here means filter tasks i.e. by any filter in a column).

great, that works :)

when a grid cell is in edit mode (double click) you can jump to the next cell with tab. How to disable that key stroke ?

just an additional information: the programatic resort takes around 50-80 ms compared to the active sorter which extends by > 8 seconds and the sorters do not sort new objects added to the store

we reduced the events, but with the sorters it is still the same:

reducedEvents.jpg, no sorters
reducedEvents-sorters, sorters

your hint: if (!changesetApplied){ var applyObject = { updated:[] }; applyObject.updated.push(treeDataObject); gridComponent.project.suspendChangeTracking() gridComponent._store.applyChangeset(applyObject); gridComponent.project.resumeChangeTracking() } reduces needed time by around 20% ;)

some more findings around the sorting:
we have removed the sorters from the store and call store.sort after applying new data. This is really fast (enough). We'll check your findings above