[Mahir Al RahmanParticipant]

Perfomance problem on:

1- UpdateRow (alone, without beginUpdate/endUpdate) inside and outside the loop
2- UpdateRow (with beginUpdate/endUpdate) inside and outside the loop
3- UpdateRow (without beginUpdate/endUpdate) inside and outside the loop
4- UpdateRow (with beginUpdate / endUpdate) inside and outside the loop

However. i didnt test setcellvalue, i am gonna test that.

/Mahir

[Mahir Al RahmanParticipant]

Hi Peter,

Seems like you misread my previous post or i didnt clarify enough. I apologize for that.

I wrote IF i handle the array (not the tree’s records, the array that the tree has been populated from) for aggregations and updates and then i destroy destroy the treegrid on each update process, will i still be facing the lose of expanded nodes state? since the dom removes by calling destroy

/Mahir

[Mahir Al RahmanParticipant]

“If you just update data, you will not have any memory leaks due to the simple reason that the widget uses the same Array of data and simply updates the Array value and updates the DOM Node.”

Peter, you wrote this in your previous comments. My question now is, if i :

1-handle the array for aggregations and updates
2- destroy the treegrid on each update process

I will still lose the state of the expanded nodes, that applies to the jqxTree i guess?

/Mahir

[Mahir Al RahmanParticipant]

Dear Peter,

Thank you for replaying. True, i don’t use destroy in my code, because using the destroy on the treegrid will make me losing my data/all expanded nodes ( almost everything), populating a destroyed treegrid from the beginning will reset the treegrid.

I want to keep all behaviors AS IS.

Is there anything i can use?

/Mahir

[Author]

Posts