-
-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get scroll position of dragable line chart #1272
Comments
it doesn't necessarily need to be the scroll position but more importantly an indicator telling that I have reached the newest (most right) value in the line chart. |
would |
Unfortunately not as the |
Why highestVisibleXIndex does not work for you? The entry contains xIndex, so you just have to compare highestVisibleXIndex and your max xIndex value. I couldn't find a more dedicated API for this right now. But I think what we could try here is to manually calculate the current offset, like contentOffset concept, though we don't have contentOffset property.
Sorry it has been some time for me doing the matrix calculation, it's a little rusty. You can take a look at One example I can come up right now: We know the last entry, so we know the highest xIndex; this xIndex can be project to pixel coordinate system via |
I think I have seen such questions before, but couldn't find the old issues now Also, please take a look at |
It doesn't work because I am using a |
you implemented your own |
like this: |
hmm.. seems I can't provide more help here.. maybe ask @danielgindi |
Well if you're adding a dragoffset - then of course But you need to work with the viewport here. So what I'm saying is- if you make a PR with the counterparts for |
Probably a very simple question: I have created a simple dragable/scrollable linechart and need to get the current scroll position to determine whether I have reached the end of the chart. For more details see: http://stackoverflow.com/questions/38606896/get-scroll-position-of-dragable-linechart
The text was updated successfully, but these errors were encountered: