Search

This example shows how to use the remove option of the stateRestoreConfig configuration object to disable the removal of states using stateRestore by setting the option to false. The default for this option is true meaning that removal is allowed.

This example shows how to use the create option of the stateRestoreConfig configuration object to disable the creation of states using stateRestore by setting the option to false. The default for this option is true meaning that creation is allowed.

This example demonstrates how the API methods within StateRestore can be used without the standard buttons being present. Use the input element to the right to input an identifier. The other buttons will then implement the relevant API methods. List Update Existing State Add New State Load Remove Remove and skip modal Remove All Remove All skipping modal

This is the section for showing the key configuration options that are available with StateRestore.

This example demonstrates all of the API methods that are available within StateRestore and how they can be used outside of the usual buttons interactions. Use the input element to the right to input an identifier. The other buttons will then implement the relevant API methods. Save Add State Load Remove Remove and skip modal Remove All Remove All skipping modal

This example shows how the StateRestore extension can be operated over ajax when setting the ajax option of the stateRestoreConfig configuration object to be a function. When ajax is a function, it will be called when the following actions are taken. loading states into StateRestore save rename remove The function takes two arguments, the first of which is an object. The first value on the object (action) is one of the above actions as a string. This will allow your function to act accordingly. The second value on the object, stateRestore is another object. The keys of this object indicate which state the action is taking place on, the corresponding value is either the state to be saved, or in the case of rename, the new name for that state. There is no stateRestore property when loading states. The second argument taken by the function is a callback that should be called when loading in states to StateRestore. An object of the same structure as the preDefined option of the stateRestoreConfig configuration object should be passed in to this function in order to load the states into DataTables. This example demonstrates how IndexedDB could be used to store states, implemented through idb.

This example shows how the StateRestore extension can be operated over ajax. To do this the ajax option of the stateRestoreConfig configuration object has to be set to a url that will be used when attempting to save the states. States are then loaded again via the tables own ajax url. If there is a stateRestore property in the json that is initially passed then the states present there will be loaded into the table. It is worth noting that we only provide the client side implementation. You will have to write your own server side implementation to save states for longer than the current session. The Scroller extension is also being used here. This is because it is a common use of loading over ajax.

Select provides a number of buttons that can be used with the Buttons extension for DataTables. Buttons is a framework providing common options, styling and API methods for buttons that can control a DataTable. The selection control buttons made available by Select are: selected - Enabled only when one or more items are selected selectedSingle - Enabled only when a single item is selected selectAll - Select all rows selectNone - Deselect all rows selectRows - Select rows selectColumns - Select columns selectCells - Select cells All of these button types are demonstrated in this example.

As well as the selection control buttons, Select also provides a button that can be used to toggle a filter that will reduce the display to just those rows in the table which are selected: showSelected. This example demonstrates this button. To see it in action, select one or more rows and then toggle the button by clicking on it. The display will reduce to just the selected rows. Toggle the button again and the filter will be removed.

This example demonstrates the searchPanes.cascadePanes feature working alongside the searchPanes.viewTotal feature. Cascading panes allow the panes to be filtered based on the values selected in the other panes. Both searchPanes.cascadePanes and searchPanes.viewTotal are false by default.

rendering continues after the init event. (See console log)

columnDefs: columnDefs }); console.log('after datatable init'); console.log(contactTable); $('#submit-edits').on('click', function(ev) { ev.preventDefault();

id: function () {}, index: function () {}, init: function () {}, invalidate: function () {}, length:

the values inside each init functions I need: e.g.,

editor: facturearticleEditor, enabled: false, init: function (dt) { factureTable.on('select deselect',

well. Also, the Datatable init fails; the Ajax call

at _.enable (requireLib.js:1152:1) at _.init (requireLib.js:783:1) Code used is:

configuration example does not init the datatable. I have

I found it : I put seriesChart10years = []; only in the init- footerCallback and all the charts are ok now.

Please post your Datatables init code and any relevant