-
-
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
No circle is drawn on a line chart when there is only one data. (version 3.2.2 only) #3848
Comments
I'm experiencing the same issue, also, adding more points the first circle is not displayed. |
Actually, the first point doesn't have a circle. It doesn't matter if there's only one data point or more. |
YusukeOba
pushed a commit
to YusukeOba/Charts
that referenced
this issue
Feb 25, 2019
phughes
added a commit
to phughes/Charts
that referenced
this issue
Mar 8, 2019
jjatie
pushed a commit
that referenced
this issue
Mar 9, 2019
Resolved by #3891 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What did you do?
I updated the Charts library from 3.2.1 to 3.2.2.
What did you expect to happen?
When a line chart has just "one" entry data, the chart shows a circle to indicate the data.
v3.2.1 (with highlight / It draws a circle. correct.)
v3.2.1 (without highlight / It draws a circle. correct.)
What happened instead?
No circle was drawn on the chart.
*
chartDataSet.drawCirclesEnabled
is always set as TRUE.The problem happens when there is only "one" entry.
(But if there are more than two entries, it works fine.)
v3.2.2 (with highlight / No circle was drawn. wrong)
v3.2.2 (without highlight / No circle was drawn. wrong)
*When I switch it back to the version 3.2.1, it draws a circle (expected behavior).
Charts Environment
Charts version/Branch/Commit Number: 3.2.2 (latest version)
Xcode version: 10.1 (latest version)
Swift version: 4.2.1 (latest version)
Platform(s) running Charts: iOS
macOS version running Xcode: Mojave 10.14.3 (latest version)
Sample Code
FYI
The issues/fixes below may be related to this problem.
#3798
#3164
The text was updated successfully, but these errors were encountered: