My question is, can this be prevented (I wondered about something like a legend.pg in the options, but nothing similar seems to exist -- or is very well hidden).
My workaround which was getting very unwieldy and impractical was a hack that found the current page prior to the redraw (regex matching on the <current pg>/<total pgs> display then programmatically triggering the right arrow the correct number of times to get me where I want to be following the redraw).
Any suggestions would be appreciated!
There seems to be a simultaneous preponderance of several people interested in legend paging and control of legend items, both here and internal to Google. There is currently a lack of support for this set of features, but given the interest, I expect we will provide a solution soon.
I am particularly impressed by your hack, and the extent you are willing to go to get the desired effect.
Thanks so much for the quick reply, Daniel!
That would be fantastic if Google could add support for this functionality. That is interesting that all of the interest in this functionality arrived around the same time -- seems like it would be quite useful for many advanced use cases.
For what it's worth, my 2 cents on what would be useful (specific to my use case) would be, in order of importance:
1) getter/setter to change page following chart being rendered,
2) as mentioned in the initial post, option support for changing which page is active on render (my thinking is that using option 1 may end up with the user seeing a flicker if the chart is first rendered, then the page is immediately changed), and
3) a getter for how many pages there are in the chart.
That would be fantastic if Google could add support for this functionality. That is interesting that all of the interest in this functionality arrived around the same time -- seems like it would be quite useful for many advanced use cases.
For what it's worth, my 2 cents on what would be useful (specific to my use case) would be, in order of importance:
1) getter/setter to change page following chart being rendered,
2) as mentioned in the initial post, option support for changing which page is active on render (my thinking is that using option 1 may end up with the user seeing a flicker if the chart is first rendered, then the page is immediately changed), and
3) a getter for how many pages there are in the chart.
댓글 없음:
댓글 쓰기