Search

describes the checkbox selection options in detail, but please

The examples in this section demonstrate the basic initialisation and options of FixedColumns.

DataTables' built-in column visibility options (

to provide additional editing options for the end user.

and row selection interaction options. While it is sometimes

a number of configuration options available to it, including

to provide full CRUD options for this collection editor.

of its field type options and multi-row editing abilities,

with a list of options retrieved from the server.

for DataTables loading language options (which is configured with

Editor has a default option: , { "type": "radio", "label": "Days:", "name": "days", "ipOpts": [ { "label": "All", "value": "all" }, { "label": "Selected:", "value": "selected" } ], "default": "all" }

That would be great - thanks! Allan

Will be doing so in future :-)

Now that does look interesting. Thank you for the link. I'll investigate this more closely once DataTables 1.0 is out of the door. Allan

I was facing same problem. I followed this discussion and solved it. Thank you guys for your effort. Here is the final fix [edit only the mRender method]: [code] "mRender": function( data, type, full) { // You can use as well if you want return 'edit'; } [/code]

[quote]allan said: ColReorder will fire the 'column-reorder' event[/quote] could you please give a simple example on how to bind functions to column reorder event? i can't seem to find any. thanks

@allan, thanks for the comment! Yes indeed that was the issue. .hide() is display:none, so that explains it. What I ended up doing is having the css hide (visibility:hidden) the table and make the surrounding div height="40px", then with jquery used my click to show make the surrounding div height="auto" and the table visibility:visible. Looks fairly similar to what I was doing before and the PDF table data looks great. Super script Allan! Thanks a bunch for your work.

Thanks a lot it worked.

turns out there was already a feature IN datatables that allows the value of one column to serve as the search value for the display in another...what an amazing tool.

Does that assume that the 100 values loaded is the complete data set? If not, then how would this cope with the fact that the 101st record might be shown after filtering, but all the records already loaded don't meet the filtering requirements - so the user would be shown "no records" if only filtering on the client-side. I can see that this could be useful in some cases, but as I mentioned back in 2010, server-side processing is an all or nothing thing - either all of the processing is done at the server-side, or it is all done on the client-side. I think the potential for things going badly wrong with a mix of the two is quite great! Allan