Well,i was a bit in a hurry,maybe the problem is not fixedheader finally.
I am still experiencing the same problem.
I mnaged to make it work at some point by removing pieces of code.
I will let you know.
I agree the documentation for createdRow and rowCallback are not clear about which to use when. createdRow is executed once at initialization while rowCallback is called each draw. rowCallback is needed when the data can change. The rowCallback docs don't make it clear that only those rows on the current page will be processed.
However the deferRender docs are clear that only the page displayed will be processed:
As an example to help illustrate this, if you load a data set with 10,000 rows, but a paging display length of only 10 records, rather than create all 10,000 rows, when deferred rendering is enabled, DataTables will create only 10.
Answers
Could you create a test demonstrating that, please.
Well,i was a bit in a hurry,maybe the problem is not
fixedheaderfinally.I am still experiencing the same problem.
I mnaged to make it work at some point by removing pieces of code.
I will let you know.
Finally,i made it work!i have spent 4 days trying to find the solution.
The only 'good' combination is using
rowCreated(notrowCallback) and nodeferRender.deferRenderruined it.Any thoughts ?
When to use
rowCreatedvsrowCallback?I think in the near future you should consider making some complex examples which will include many different functions-plugins-filters .
Thank you.
Glad you got it working.
I agree the documentation for
createdRowandrowCallbackare not clear about which to use when.createdRowis executed once at initialization whilerowCallbackis called each draw.rowCallbackis needed when the data can change. TherowCallbackdocs don't make it clear that only those rows on the current page will be processed.However the
deferRenderdocs are clear that only the page displayed will be processed:Kevin