[pager] NaN size

[Shinobi666]

Hi,

First things first, thanks to those who have worked on this jquery plugin! It made my day! ^^

I have some issue with the size of the addon pager when I do not use a number. The matter already occured apparently : #35
Unfortunately, the fix doesn't seem to resolve my problem.

I'm still a novice, so maybe I'm doing something wrong. I'm hoping someone would have the right knowledge to help me out ^^

I do not use a select field to choose the number of lines by pages in my tab but some input field where is registered the user's preferences.
But if I try to use the value of my input, the pager is effective only on the first page (or I have to do use some trick like using the original select field with my value selected and a style display: none;)

Here is an example :
http://jsfiddle.net/5aMhh/

On the first page, I have my five recordings but if I try accessing to the second, a weird behaviour occured (all the recordings but the ones of the previous pages appear).

Therefore, I can't have a pager size like $("#test").val() for the moment but a raw number will work fine.
I hope there is a way to avoid this issue ^^

Best regards,

David

[Mottie]

Hi David!

Actually the size option wasn't meant to have anything other than a number as a value. But, you could change your input to use HTML5 number type of input (demo):

Page size: <input id="test" type="number" min="1" value="5" />

Then update the pager when the size changes:

$('#test')
    .attr('max', $table.find('tbody tr').length)
    .change(function(){
        $table[0].config.pager.size = $('#test').val();
    // "update.pager" is different in that it will update both the table and pager
    // using "update" alone won't update the pager - I might fix this in future versions
    $table.trigger('update.pager');
    });

The number type doesn't work in older browsers, but it will gracefully fallback to a text type input.

[Shinobi666]

Hi Mottie,

Thanks for the quick answer! :-)

It didn't even cross my mind that my issue could come from the type of the value since it worked fine for the first page. Moreover, the natural bahaviour of the plugin is to receive the value of a select field which isn't either a number input, right?
Anyway, thanks for the tip! ^^

For information, the example in your demo works only if you do not change dynamically the input number. In fact, you have exactly the same problem as me with an input text, it works fine for the first page and then, everything falls apart if you try to access the next one.
I do not need to change the size with a trigger but I figure you may want to know that ^^ (maybe it would be fixed by storing the value and binding some action on the event "pagerChange")

Spring MVC 3 do not support the new tags HTML5 (in the case you want to bind input fields with some POJO on the server side). What's more, it doesn't render well in IE8 and Firefox so I'd rather prefer to use my input of type text.
If you have any suggestion to get round this problem (well, it's not really one if I do not use the plugin as it's meant to be used :p), it would be great.
Worst case scenario, I use an invisible select field with my value selected. But maybe there is a cleaner way to do it :-)

Thanks again for your feed back!

Best regards,

David

Edit : I use the function parseInt during my pager's size initialization and it works like a charm now... Maybe, it would be useful for other users to automate this process in the plugin (but maybe I was thinking outside the box and there is no point in automating something like that :p).
Anyway, thanks for telling me the problem was the type! That was the key to resolve my issue ^^

[Mottie]

Hi David!

Hmm, I think in the next update I'll just add a way to change the page size like this:

$('table').trigger('pageSize', 15);