Problem refreshing headers with different number of columns

[bakayolo]

When refreshing datas and headers with differents datas, the tab is refreshed with new datas but sometimes and old column didn't desappear.
My usecase :

1. 2 columns : "Name" and "Values".
2. I refresh with 2 others columns "Age" and "Values"
3. I have 3 columns "Name" (datas empty), "Age" and "Values".
4. Others problemes, the column's order is not respected. I want "Values" always at the last position.

Code:
$scope.tabdatas = [{}];
$scope.gridOptions = {
enableFiltering: true,
enableSorting: true,
data : 'tabdatas',
columnDefs: []
};

function(data) {
var tab = JSON.stringify(data.tab);
$scope.tabdatas = eval('(' + tab + ')');
$scope.gridOptions.columnDefs.length = 0;
angular.forEach(Object.keys($scope.tabdatas[0]), function(key) {
if (key.toLowerCase() == "values") {
$scope.gridOptions.columnDefs.push({ field: key, enableFiltering: false, type: "number" });
} else {
$scope.gridOptions.columnDefs.push({ field: key, type: "string" });
}
}

[bakayolo]

The tab keep always in memory the columns which has displayed first.

Example:

1. First display : "Name" and "Values".
2. I load others headers and datas "Age", "Name" and "Values". It display "Name", "Values" and "Age".
3. Etc.

[PaulL1]

There is work underway at the moment on column reordering ( @jpuri ) and I think it would also address this issue. It will allow grid 3.0 to respect the column ordering in the columnDefs, rather than using it's own.

[PaulL1]

A couple of questions:

1. What version are you using?
2. Why are you using JSON.stringify then eval? Seems unusual
3. Is length on an array really a settable property? I haven't seen that usage before

[bakayolo]

Thanks for your response.

1. I'm using the last version "unstable".
2. I removed the "JSON.stringify" and the "eval". I used an other method before, it's because i needed this.
3. I think, it's working for me. Maybe it's not the good solution. "array.lengt = 0" or "array = []" seem to be the same.

[c0bra]

array.length = 0 empties the array. array =[] reassigns the variable to a
new reference.
On Oct 2, 2014 2:07 AM, "bappr" notifications@github.com wrote:

Thanks for your response.

1. I'm using the last version "unstable".
2. I removed the "JSON.stringify" and the "eval". I used an other method
   before, it's because i needed this.
3. I think, it's working for me. Maybe it's not the good solution.
   "array.lengt = 0" or "array = []" seem to be the same.

—
Reply to this email directly or view it on GitHub
#1645 (comment).

[PaulL1]

OK, I pushed a change yesterday that may have fixed this - refer #1670, which in turn was aiming to fix #1665. Could you check whether this has resolved the issue for you?

[bakayolo]

Perfect!
This has resolved the issue for me. Thanks. :)

I close this issue.