-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Multiple XY LineChart support #1
Comments
@Cloudo |
@Cloudo Maybe you can look for the demo in ScatterChart. |
Thank you for adding ScatterChart example. It is exactly what I was looking for. |
Fix issue in Brush where updateScale executed setState in constructor
I’m working on a chart with several reference areas, some of which extend past the canvas bounds. Though I want to draw the part of the reference area that lies on the canvas, it doesn’t make sense to draw the part that spills out. It's possible to grow the canvas to accommodate the reference area by specifying `alwaysShow`. Though after thinking about this for a while, it seems that _both_ these things should be possible: to show reference items which are partly off the canvas, and to extend the chart domain to accommodate reference items. This deprecates the `alwaysShow` prop, and adds an `ifOverflow` prop which supports four values: - `ifOverflow="discard"` (default) – If the reference item falls partly outside the canvas, don't display it. This is the old default. - `ifOverflow="extendDomain"` – If the reference item falls partly outside the canvas, extend the domain so it fits. This is the old `alwaysShow` behavior. - `ifOverflow="clip"` – If the reference item falls partly outside the canvas, clip it to the canvas. - `ifOverflow="keep"` – If the reference item falls partly outside the canvas, draw it anyway.
Update tooltip data on rerender #2150
I really impressed by your work.
Is there any support for LineChart to generate lines with not equal sets of
x
coordinates?Example: http://c3js.org/samples/simple_xy_multiple.html
Thanks!
The text was updated successfully, but these errors were encountered: