jQuery Grid Plugin - jqGrid - Topic: Triggered Events 4.3.2 http://www.trirand.com/blog/?page_id=393/discussion/triggered-events-4-3-2 Simple:Press Version 5.7.5.3 tony on Triggered Events 4.3.2 http://www.trirand.com/blog/?page_id=393/discussion/triggered-events-4-3-2#p27287 Discussion http://www.trirand.com/blog/?page_id=393/discussion/triggered-events-4-3-2#p27287 Hello,

Of course you canu use afterInserRow in grid parameters instead as triggerHandler.

More on this you can find here

Regards

]]> Mon, 10 Sep 2012 19:09:01 +0300 rknorp on Triggered Events 4.3.2 http://www.trirand.com/blog/?page_id=393/discussion/triggered-events-4-3-2#p27269 Discussion http://www.trirand.com/blog/?page_id=393/discussion/triggered-events-4-3-2#p27269 A lot of new triggered events were added in 4.3.2.  They are raised by calling jQuery triggerHandler.  Because triggerHandler is called instead of trigger, the events do not bubble up the DOM.  This makes it impossible to use .live() or .on() against the document and have the events bubble up and get handled.

Here's my problem.  I have a grid. After the grid is set up, I call (for example):

$(document).on('jqGridAfterInsertRow', gridSelector, {}, function(e, rowId, rowData) {

    // do some work

});

My handler doesn't get called because jqGridAfterInsertRow doesn't bubble up to the document.

If I use:

$(gridSelector).on('jqGridAfterInsertRow', function(e, rowId, rowData) {

   // do some work

});

then things work great – until I call GridUnload and reuse the table element for a new grid with a different column model.  GridUnload removes my handler.

Is there a reason that you chose to use triggerHandler instead of trigger for these new events?

]]> Thu, 06 Sep 2012 20:08:48 +0300