Permalink
Commits on Mar 9, 2017
  1. Version bump

    beneverard committed Mar 9, 2017
Commits on May 21, 2014
  1. Version bump (1.4)

    beneverard committed May 21, 2014
  2. Merge branch 'wm-set_curret_page_first' of github.com:wm/jqPagination…

    beneverard committed May 21, 2014
    … into wm-wm-set_curret_page_first
  3. Improve getter reliability

    beneverard committed May 21, 2014
    Especially as we may not be passing a value parameter if setting multiple values
Commits on Apr 9, 2014
  1. Reorder of updating max_page, current_page

    wm committed Apr 9, 2014
    This commit changes the order in which we set current_page and max_page
    to ensure we always set current_page first.
    
    This will prevent the error:
    
        jqPagination: max_page lower than current_page
    
    from occuring when we simultaneously update max_page and current_page
    and max_page is less than the old current_page.
Commits on Dec 1, 2013
  1. Moved demo.css to Sass

    beneverard committed Dec 1, 2013
Commits on Jul 26, 2013
  1. Version bump (1.3)

    beneverard committed Jul 26, 2013
Commits on May 25, 2013
  1. Corrected handling of setting the properties of multiple pagnation el…

    m-hume committed May 25, 2013
    …ements
    
    When setting the options of multiple pagnation instances only the first instance was affected.
    Consider the following
    $('#paginationTop, #paginationBot').jqPagination('option', 'current_page', 5)
  2. Set an option without triggering the paged event

    m-hume committed May 25, 2013
    Usage:
    .jqPagination('option', {key: value[, key: value][, trigger: true|false ]})
    
    Legacy operation is maintained but now you can set multiple properties with one call and specify if you want the paged trigger to fire
    
    the following sets the max pages to 10 and the current page to 5 whilst not triggering paged 
    .jqPagination('option', {
        max_page: 10,
        current_page: 5,
        trigger: false
    });
Commits on Feb 4, 2013