I dont't recommend you to use modal:true property. You can't use it in the combination with jQuery UI. See the answer
Hello sebastiancb,
you can do two things:
1) use option
editoptions: { style: "text-transform: uppercase" }
to display the text directly in uppercase. It will display the thex in uppercase only, but not convert the data.
2) conver the data from the corresponding column in upper case. In case of usage form editing you can use beforeSubmit callback which you can set for example expanding $.jgrid.edit:$
.extend($.jgrid.edit, {
By the way. If you have interest in the part of my suggestions about the usage of
Hi pbor,
you can get the value from ts.p.totaltime, like any other property of ts.p, by usage of getGridParam method:
loadComplete: function () {
Hello Micheale,
I see that you use my demo from the answer. I tried to describe the solution in my previous answer. You can see the modified demo here. I used modified version of the beforeShowForm
Hello Tony,
if you have a little time in the next two weeks it would be nice to make some small (or less small) improvements in jqGrid. I just wanted to post you some my ideas, just some subjects which are seems the mostly interesting from my point of view:
Hello micnie2020,
I agree with Tony, that it's difficult to understand what you mean. I try to guess. I can suppose that you add some additional elements in the form inside of editing for callback like beforeShowForm. If you don't use recreateform: false then your current code add the same custom element every time when the form will be opened.
It seems to me that you should modify your code a litte and verify whether the custom elements are already in the form. You should add the custom elements only when there are not yet in the form. If you would add some custom class or id to one from the added elements then the corresponding verification will be very simple.
Best regards
Oleg
Hello Tony,
I postes the changes as
@Inara: You can use dynamicLink formatter if you want. See the answer
Hello Tony,
I would like to post some small pull requests, but the the previous one is still unanswerd.
Look at the answer for example where I suggested very simple new jqGrid method destroyFilterToolbar. It seems to me that the method could be practial for other users. Additionally I found some other small bugs. I could post the fixes as new pull requests, but I don't know how to post the fixes without mixing the fixes with previous pull request. Could you please read my previous pull request
Hello,
in my opinion it would be gut to ask Tony to create more frequently minor jqGrid releases. For example one could create 4.4.2 now.
If you need to create jquery.jqGrid.min.js yourself you can do the following: If you would open
Hello Tony,
I want remind you about the pull request. I can't post any other change request till you not process it.
I think that my suggestions from the request have no side effects. It sould only improve the performance and the ability to make changes in the grid for example to change id.
I wanted to post another pull request for inline editing for the case that one uses column with the name 'id' or for the case that one want edit the grid with editable column having key:true property. The code which I wanted to suggest will work in the cases which I imaganed me with exception of formatter:”actions” in the current implementation.
Best regards
Oleg
I unswered here on your identical question. I posted the demo which do the same what you described, but it have no described problem. So I suppose (like Tony wrote you before) that you should examine your code (which you not posted) for the problem. If you do found a bug in jqGrid you should provide the corresponding demo (the test case) which can be used to reproduce the problem.
Regards
Oleg
jqGrid uses jQuery UI CSS. jQuery UI don't support quirks mode too. The usage of quirks mode means that you are in the time before publishing of HTML 4 in december 1997. All web browsers created in the current year thousend (starting with 2000) support HTML 4. So I think that you should probably fix your code by including some statement.
If you don't use you can't use practically any recent JavaScript library. Even if some features will be work you will be definitively in not tested and not supported environment.
Regards
Sorry, my last suggestion was based on my *original* code where the value of rowID was undefined. One uses $.extend with input parameters. So one can't ovewrite any other value with the undefined value. If you use null as the default value then rowID will never been undefined, but it's not a real problem. So your previous suggestion will work exacly so good as the last one. Sorry for the misunderstanding.
Regards
Oleg
Copyright 2014 TriRand LtdAll Rights ReservedRSS
Back to Top