Forum
20:08
17/11/2010
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?
19:09
Moderators
30/10/2007
Hello,
Of course you canu use afterInserRow in grid parameters instead as triggerHandler.
More on this you can find here
Regards
For professional UI suites for Java Script and PHP visit us at our commercial products site - guriddo.net - by the very same guys that created jqGrid.
Most Users Ever Online: 715
Currently Online:
32 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
OlegK: 1255
markw65: 179
kobruleht: 144
phicarre: 132
YamilBracho: 124
Renso: 118
Member Stats:
Guest Posters: 447
Members: 11373
Moderators: 2
Admins: 1
Forum Stats:
Groups: 1
Forums: 8
Topics: 10592
Posts: 31289
Newest Members:
, razia, Prankie, psky, praveen neelam, greg.valainis@pa-tech.comModerators: tony: 7721, Rumen[Trirand]: 81
Administrators: admin: 66