Search

how do I update the row inside createRow function "createdRow" : function( nRow, aData, iDisplayIndex ) { var $row1 = $('td:eq(1)', nRow).find('.progress').eq(0); $.ajax({url: "url",dataType:"json", type:'POST',data:{ data:$data}, success: function(result) { fnUpdate( nRow, false); }, }); },

That does work!

I have something almost identical, so I think I can help! In the initialization, I use the columns option. If I'm not mistaken, aoColumns is the same thing, using legacy nomenclature. My columns for one of my tables looks like this: "columns": [ {"data": "username", "title": "User Name" }, {"data": "homeDirectory", "sortable": false, "title": "Home Directory"}, {"data": null, "sortable": false, "defaultContent": fcapp.render.tools("user"), "createdCell": function (td, cellData, rowData, row, col) { $(td).addClass('toolcell'); } } } ] So, the first two columns contain data found in the JSON, with the keys "username" and then "homeDirectory". The third column contains action buttons like yours. So the difference with this column is that the data attribute has a null value and defaultContent is populated with markup. The method fcapp.render.tools("user") that I supply to defaultContent is just an HTML concatenator and returns a string of HTML. I also add the class "toolcell" to the entire cell in the createdCell callback so that I can potentially bind a click listener to the whole cell instead of the contents, as well as streamline any CSS that goes into that cell.

Hi Thanks, that works. Peter

Working! You're awesome :-)

Sorry about the double thread btw :/

I'm a bit slow on this one - sorry - however, the good news is that it is fixed in the nightly version of Scroller and should be released as a stable version tomorrow. Allan

How does this relate to DataTables?

Worked like a charm :-) Thank-you for the quick response and help.

You are correct - this is a global configuration. At the moment this is really the only way. I wonder if I should make the error event cancellable. That would, at least on initial thought, seem to solve the issue. You would add an event listener and then return false from it. I'm not immediately seeing any downsides... Regards, Allan