You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently aiExclude only accepts integers, but if your columns have an mDataProp (or sName) defined, we should be able to use those names. Using colreorder makes column numbers useless.
Great work on this!
The text was updated successfully, but these errors were encountered:
This is an excellent point and one I have been debating quite a bit of late with myself. There is now significant overlap between sName, mDataProp, aTargets and column indexes to refer to columns. They all serve their own purpose of course, but you are absolutely correct that there should be an easier mapping between them.
I think the correct thing to do at the moment with how things stand in DataTables 1.x is to use sName, since it is the closest to referring to each columns individually (again - the others could do that...). So yup, perfectly valid and very good suggestion!
In DataTables 2.x (when I get going on that...) I will look at tying these related properties together a lot closer, and providing mapping abilities. For example wherever you can refer to a column index, you should also be ale to refer to sName (or whatever...).
Hi,
Currently aiExclude only accepts integers, but if your columns have an mDataProp (or sName) defined, we should be able to use those names. Using colreorder makes column numbers useless.
Great work on this!
The text was updated successfully, but these errors were encountered: