Forum


16:40

08/09/2014

If you want to see my question laid out in detail, see this post I just put on Stack Overflow.
Here's my synopsis:
With each column tweak, I save the new column model to the server, for that user, and immediately start mutating the JSON to align with the new column order for that user's ajax requests. In this scenario, do I still need the remapColumns function or the permuatation variable?
Â
As it stands, since I've already 'mutated' the JSON for successive ajax requests, it is then being mutated a second time by the "perm" array that my "done" function of the column chooser sent into the remapColumns method.
After a user has used the column chooser (or has performed a column drag-n-drop) is there a way I can clear out the permutation array?
Is there a way I can adjust things so the user doesn't have to refresh their page to start using the new column order?
I've seen Oleg's recommended way to persist settings (but, I had already put this solution in place)
17:21

08/09/2014

What I think I need to do, is use remapColumns in the normal manner, initially, so that the local data already in the grid, along with it's headers, are properly re-organized.
Then, I think I need to call remapColumns a 2nd time, passing in a plain permutation that informs the grid that incoming ajax requests can be left alone.. a cell-data only permutation of [0,1,2,3,4] so that it does not affect try to map the JSON (since the server is already doing it). I'm not sure how to do this, however.
Most Users Ever Online: 715
Currently Online:
33 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
OlegK: 1255
markw65: 179
kobruleht: 144
phicarre: 132
YamilBracho: 124
Renso: 118
Member Stats:
Guest Posters: 447
Members: 11373
Moderators: 2
Admins: 1
Forum Stats:
Groups: 1
Forums: 8
Topics: 10592
Posts: 31289
Newest Members:
, razia, Prankie, psky, praveen neelam, greg.valainis@pa-tech.comModerators: tony: 7721, Rumen[Trirand]: 81
Administrators: admin: 66