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

[Bug] Double BarChart second value text mispaced #1191

Closed
skywinder opened this issue Jun 29, 2016 · 6 comments
Closed

[Bug] Double BarChart second value text mispaced #1191

skywinder opened this issue Jun 29, 2016 · 6 comments
Labels

Comments

@skywinder
Copy link
Contributor

skywinder commented Jun 29, 2016

I would like to create chart as in screenshot^
screen shot 2016-06-29 at 11 07 39

But can't place label in right position in case of 0
Please, have a look at screenshot in comment for details

@skywinder
Copy link
Contributor Author

Update: I found a solution, by adding 2 values in one BarChartDataEntry

But now I found a Bug: If bottom (second) value is 0 - them text is not displayed in the bottom, and overlapped top text. Please have a look at screenshot right value as example. I can provide code, to reproduce this issue, if needed.

screen_shot_2016-06-29_at_18_16_40

@skywinder skywinder changed the title [Questinon] Double BarChart [Bug] Double BarChart second value text mispaced Jun 29, 2016
@pmairoldi
Copy link
Collaborator

Thanks for the bug report!

@pmairoldi pmairoldi added the bug label Jun 29, 2016
@skywinder
Copy link
Contributor Author

@petester42 I already fixed it. Please wait for my little fix for this issue in 5 minutes 😉

@danielgindi
Copy link
Collaborator

@PhilJay do you know anything about this bug?

@PhilJay
Copy link
Collaborator

PhilJay commented Aug 10, 2016

Looks really weird, but I have not seen it anywhere personally.

Not sure it's a bug either. Stack values >= 0 are placed to the left of the zero line in stacked bars, negative values below the zero line. Workaround could be to add the "4" of the last bar as "-4" and then format it to "4".

@skywinder
Copy link
Contributor Author

@PhilJay It could be my option for workaround. Bit I found proper solution to fix this bug. please kindly check #1195 do you think, that this change could produce potential bugs?

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

Successfully merging a pull request may close this issue.

4 participants