-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
on column resize ajax call #9
Comments
I haven't tested this plugin with the server side implementation of data tables, and don't have much experience with using data tables that way. What ajax calls are being made? |
I have used "sAjaxSource" and used another plugin call scroller for scroll, whenever i goes down with scroll, if resize the column table goes to 1'st record with ajax call,i want to prevent them. |
Just define ajax as function, and if request hasnt changed from last one, do not forward the request to the server. |
when defining ajax as a function, u get a paramater that holds the draw Callback.. after the server responds, u apply the callback with given data. |
$('#tableselector).on('column-sizing.dt', function (e, settings) { Resolved issue. |
comment in event |
Thank you for looking into this everyone. I hope you have found an adequate solution to this problem. |
Sure......and thanks for making wonderful plugin. |
Instead of |
I am reopening this, this process should be accounted for in the future and setting the this.s.dt.oInstance.fnAdjustColumnSizing(false) will be allowed through a property of colResize |
Sorry I haven't had much time to develop this plugin as our company has moved on to other solutions with angular grid since we operate with Angular. I will continue to maintain pull requests, but I won't have much time to develop it myself. I am hoping the community will step in an fix some of these problems as well. |
As i resize column there is a ajax call going as i have bind datatable with serverside call
I want to stop ajax call on column resize, please guide me a way out.
The text was updated successfully, but these errors were encountered: