Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <pre><code> this.construct = function(settings) { return this.each(function() { config = $.extend(this.config, $.tablesorterPager.defaults, settings); var table = this, pager = config.container; $(this).trigger("appendCache"); config.size = parseInt($(".pagesize",pager).val()); $(config.cssFirst,pager).click(function() { moveToFirstPage(table); return false; }); $(config.cssNext,pager).click(function() { moveToNextPage(table); return false; }); $(config.cssPrev,pager).click(function() { moveToPrevPage(table); return false; }); $(config.cssLast,pager).click(function() { moveToLastPage(table); return false; }); $(config.cssPageSize,pager).change(function() { setPageSize(table,parseInt($(this).val())); return false; }); </code></pre> <p>This is the constructor for the tableSorter Pager plugin. As you can see it binds click functions to elements based on the config (cssFirst, cssNext, cssPrev, cssLast ). Unfortunately this means those elements must already exists in the container defined by 'config.container' This doesn't seem to be documented anywhere on the pager plugin site. But you must define (in html, or with javascript before the call to the pager function) elements with the following default classes:</p> <pre><code> cssNext: '.next', cssPrev: '.prev', cssFirst: '.first', cssLast: '.last', </code></pre> <p>I'm not sure how the table sorter will interact with your hidden rows, you may need to make some modifications to the core tableSorter functionality to get the behavior you're looking for.</p> <p>/Chris</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload