Hello Tony,
here are my table settings for such a problematic table
var newTableSettings = {
Hello Tony,
I could also reproduce it with a scrollTimeout of 80, than I reduced this to 40 and could not reproduce it (but did only try a few times).
It seems to happen when I change the scroll position while “loading …” new data from server.
Maybe I'll keep trying a bit tomorrow (and I will also watch memory and
Hello Tony,
No, your suggestion did not help with my problem. The mentioned statement (
$("*",tBody).children().unbind();
) will only unbind all events but will not clean up the following …
For example when I attach jQuery Tooltips on cells in the table, they create some JS objects and some DOM elements (DIVs) directly on the body.
So the only solution to remove those objects was using the remove method which will then invoke the widget's destroy method.
Kind regards,
Klaus.
Hello Tony,
The memory leaks seemed to be across several browsers (IE, Firefox).
I hope you didn't misunderstand – not the jqGrid itself has a memory leak – but any jQuery widget attached to the grid will not be destroyed correctly but keeps somewhere in memory.
The only solution (I found) to destroy those attached widgets (e.g. context menues or special tooltips on cells or rows) was by calling the jQuery remove method.
here is the code how I create my context menu widgets:
// attach context menues on all grid rows
var gridCompleteFunction = function() {
I've found the other posting:
http://www.trirand.com/blog/?p…..gridwidth/
I will keep watching for a bug fix.
Thank you,
Klaus.
Thank you.
That seems to fix some problems.
Another problem that sometimes occurs in my web app is the following …
… when a grid instance is already destroyed (because of a view change) at the time when an outstanding ajax-call (loading new data) completes (loading the received data into the grid) this throws an error because it can't fill the grid which was already destroyed.
I know I should prevent such situations (to destroy the grid befor all open tasks and ajax-calls are finished) but how do I know if any asyc action is still in progress?
The bad thing with JavaScript errors is, that the whole webapp crashes.
Nevertheless I like your grid control plugin. Cool and highly customizable solution. 
Kind regards,
Klaus.
… I've solved the problem, but couldn't find a real bug in my code.
maybe the problem was that I've mixed searchoptions and editoptions parameters in my colModel (because of a bug in the previuos release).
now it seems to work! 
However thank you for checking my problem.
Kind regards,
Klaus
Thank you for the quick fix on the update site.
The current download is ok (no more byte-order-marks in those files).
Hello!
What's the current state to that issue?
Is there a possibility to dynamically change the grid's colModel/colNames – i.e. add a new column without a complete rebuild of the grid object?
I've looked through several postings but didn't find a definitive answer.
Do I need the GridUnload-method or what's the easiest way to change the columns?
Kind regards,
Klaus.
Thank's for the quick answer.
Is there another method or trigger-function I can call to only reload the grid without invoking any cleanup-tasks?
(why I need this? … I would like to trigger an automatic reload of the table data periodically)
Kind regards,
Klaus.
Hello Tony!
I've tried your hint, but that doesn't solve my problem.
The search-parameters seem to be cleared on clicking the refresh button.
1) select a filter and click find …
POST http://localhost/htmlclient/server/webserver.dll
I've noticed similar problems with the definition of the value-attribute for stype:select in the search-/editoptions and my table search still does not work with the patch (of changing the order of the soptions-extend) mentioned above!
I solved the problem the following way, which in my option is not really a clean solution:
… stype: 'select', editoptions:{value:{'yes':'yes','no':'no'}}
Copyright 2014 TriRand LtdAll Rights ReservedRSS
Back to Top