-
Notifications
You must be signed in to change notification settings - Fork 231
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
TimeSeries chops off data if client width is 0 #13
Comments
I've also run into this problem when displaying graphs in jQuery tabs. |
+1 |
Yes, PRs are reviewed and merged. How would your proposed solution work? On 2 September 2016 at 00:27, Dmitry A. Efimenko [email protected]
|
I don't have a proposed solution for this yet. Similar thing happens if you apply On the topic of PRs... what about existing PRs? PR for tooltips and LineDash seem legit. I didn't look at others. |
it appears that the chart option |
(Reported by Rob Knapp)
I just discovered something about smoothie charts that I wanted to point out.
In render, you chop off the TimeSeries data based on age. If it happend more than the clientWidth*MillisPerPixel millis ago, it gets dropped.
At least on Chrome, the clientWidth of a canvas can be 0 under some circumstances.
For example, I have some smoothie charts on a JQuery tab. If I move to a different tab, the clientWidth goes to zero and all the data gets chopped off.
I've gotten around this by adding dimension.width>0 as a condition on the while loop that culls the data... but I'm sure there is a better solution... perhaps an option that grabs the dimension array once and reuses it?
The text was updated successfully, but these errors were encountered: