Skip to main content

jqgrid - close form dialog



I am using jqgrid 4.3.1 and I am using form editing with local data. The problem is the form does not close after adding or editing. Here is my code.







$('#studentset').jqGrid({

data: mydata,

datatype: "local",

colNames:['id','First Name', 'Last Name'],

colModel:[

{name:'id',index:'id', width:60},

{name:'firstName',index:'fName', width:300, editable:true},

{name:'lastName',index:'lastName', width:300, editable:true}

],

pager: '#pager',

rowNum: 10,

rowList: [5, 10, 20],

sortname: 'id',

sortorder: 'asc',

viewrecords: true,

height: "80%",

caption: "Students to be Registered",

editurl: corpUrl

});

$('#studentset').jqGrid('navGrid', '#pager', { add: true, edit: true, del: false, search: false, refresh: false },

{

recreateForm: true,

closeAfterEdit: true,

modal:true,

afterSubmit: function(data){

var myObject = eval('(' + data.responseText + ')');

$('#studentset').setGridParam({data: myObject}).trigger("reloadGrid");

}

},

{

recreateForm: true,

closeAfterAdd: true,

modal:true,

afterSubmit: function(data){

var myObject = eval('(' + data.responseText + ')');

$('#studentset').setGridParam({data: myObject}).trigger("reloadGrid");

}

},

{},{},{}

);







Notice in the edit and add options of the navGrid I have specified the relevant options. closeAfterAdd: true, and closeAfterEdit: true . But the modal form simply refuses to close. I am not sure if its a bug in this version of jqgrid.





Can someone please offer some guidance? May be, how to close the dialog manually?


Comments

  1. Ok so its logical, simply trigger the click event of the dialog close button like this. You will find the ID of the span tag using fire bug.

    $('#studentset').jqGrid('navGrid', '#pager', { add: true, edit: true, del: false, search: false, refresh: false },
    {
    modal:true,
    jqModal: true,
    afterSubmit: function(data){
    var myObject = eval('(' + data.responseText + ')');
    $('#studentset').setGridParam({data: myObject}).trigger("reloadGrid");
    $(".ui-icon-closethick").trigger('click');
    }
    },
    {
    modal:true,
    jqModal: true,
    afterSubmit: function(data){
    var myObject = eval('(' + data.responseText + ')');
    $('#studentset').setGridParam({data: myObject}).trigger("reloadGrid");
    $(".ui-icon-closethick").trigger('click');
    }
    },
    {},{},{}
    );


    Hope someone benefits from this.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex