Skip to content
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

Charts 3.0.1: rendering artifact on iPhone 4s & iOS 8.1 #1956

Open
clear-m opened this issue Dec 13, 2016 · 7 comments
Open

Charts 3.0.1: rendering artifact on iPhone 4s & iOS 8.1 #1956

clear-m opened this issue Dec 13, 2016 · 7 comments
Labels

Comments

@clear-m
Copy link

clear-m commented Dec 13, 2016

Hi!
I am faced some strange chart rendering artifact on small screen of iPhone 4S with iOS 8.1 and Charts 3.0.1.
The issue reproduced with charts demo project in case of huge x values in ChartDataEntry.
Please, have a look at diff_patch.txt
Thanks!

@liuxuan30
Copy link
Member

Gees, I applied that patch and I found 4S is removed from the simulator.. Can you post a screenshot to show what's the artifact?

@clear-m
Copy link
Author

clear-m commented Dec 14, 2016

Ok - no problem - here is the screen of LineChart demo with patch applied:
simulator screen shot 14 2016 9 00 21
and with other presets:
simulator screen shot 14 2016 9 03 01

@liuxuan30
Copy link
Member

oh no.. I don't see what's wrong with the first image, but the second one is a mass.. Would you be able to debug and fix? I don't have a 4S env to test..

@liuxuan30 liuxuan30 added the bug label Dec 15, 2016
@cartmanguo
Copy link

I think this is the the same issue in #1679 ,try to use a small number for x value.
If you want to use unix timestamp,you can use the current timestamp minus the timestamp of the beginning time of a day.
example:
2016/12/15 13:51:3(1481781063) - 2016/12/15 0:0:0(1481731200) = 49863,so use 49863 as the x value of an entry.And add the timestamp(1481731200) in stringForValue method in your AxisValueFormatter Class

@clear-m
Copy link
Author

clear-m commented Dec 15, 2016

Thanks you guys for an answers!
I already did such x truncations but only as a workaround.
Yes, I think that the issues are mots likely related

@clear-m
Copy link
Author

clear-m commented Dec 15, 2016

I am also thinking that this issue is relative with #1851 too

@liuxuan30
Copy link
Member

hmm.. Guess we need @danielgindi to review this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants