pagingButtonsConfiguration='auto'

[Frodo Heisenberg]

     function drawTable() {

    var pageSize = 20;  

    var cssClassNames = {'headerRow': 'goog-visualization-table-tr-head',

                'tableRow': 'google-visualization-table-tr-even', 'oddTableRow': 'google-visualization-table-tr-odd', 

                'tableCell':'google-visualization-table-td', 'selectedTableRow':'google-visualization-table-tr-sel'}; 

       var options = {'showRowNumber': false, 'allowHtml': true, 'cssClassNames': cssClassNames}; 

       var data = new google.visualization.DataTable();

       options['page'] = 'enable';

       options['sort'] = 'enable';

       options['pageSize'] = pageSize; 

       options['pagingButtonsConfiguration'] = 'auto';

........

Now with the new version of Google Visualization API the page numbers buttons doesn't appear.

Any solution, please?

Many thanks!

[Daniel LaLiberte]

This configurePagingButtons options is not documented and it is not exactly clear why one would need it.  The buttons ought to show when needed and allow random access rather than being restricted to only one direction or the other, even if at the beginning or end of the list.   This is essentially the 'auto' mode.

I guess this option would make more sense when you do your own paging, fetching more data dynamically, so you would also manage which buttons should be enabled.  

But this option does work correctly when page buttons are displayed at all, which is when paging is 'enable'd and pageSize is non-zero.  Both buttons show, but the disabled buttons are grayed out.  So that might be a good enough work around for now.  Specify a pageSize that is larger than the number of rows you have, and only 1 page will be used.

But perhaps there is a different kind of problem involving the latest release.  The paging buttons are now displayed in a float: left that should be positioned at the bottom of the chart area, but there may be some situation in which the height of the chart excludes the paging buttons.  Can you check the HTML directly to see if they are present, but just not visible?

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/d/optout.

--

Daniel LaLiberte  - 978-394-1058

dlaliberte@Google.com   5CC, Cambridge MA

daniel.laliberte@GMail.com 9 Juniper Ridge Road, Acton MA

[Frodo]

Old version:

New version:

I've changed the height of the chart bur the buttons don't appear and they aren't present in HTML.... ¿?

--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/QUIHQu-YzD4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualizati...@googlegroups.com.

[Daniel LaLiberte]

Frodo,

Your images do prove that you do have a problem, but it appears you are doing something with the width and height of the container to cause the page number buttons to wrap to a new line after previous and next buttons.  

If you can send me a link to your page, I will be happy to look into it.  Better if you can produce a simpler case that demonstrates the same problem.  But I can't really help unless I can see the problem to figure out why it is happening.

[Frodo]

Daniel,

     Here you are 

     In this simple table with pageSize=2  I think the page number buttons should appear like the previous version.

Thanks a lot!

[Daniel LaLiberte]

It turns out that since you are loading '1.X' you are actually getting 1.1, which is still in the process of being updated to be the same as 1.0.  If you load '1.0' instead, it works fine.

I don't know why the 1.1 is broken this way, but it should be fixed as soon as the update finishes.