I implemented LineChart in my project and tried to subclass LineChartRenderer in order to change offset of values that are drawn in func drawValues(context: CGContext). The problem is that the only option is to copy all code of this method from LineChartRenderer into my subclass, but there are warnings, because _xBounds property has internal protection level.
What did you expect to happen?
I would like to be able to control value position of DataSet entries on LineChart. For example, in LineChartRenderer in func drawValues(context: CGContext) there is an alignment option, which is always set to .center, but I need to set it to left.
Thanks for the detailed report! We could add an option for text alignment. What exactly are you trying to achieve? Maybe there is already a way to do so without modifying the library.
Would be great indeed to be able to change value offsets.
For example, I would like to plot my values BELOW my scatter chart shapes, rather than above them.
Is this possible at all with the current library? From reading this ticket I get it's not at the moment..
What did you do?
I implemented LineChart in my project and tried to subclass LineChartRenderer in order to change offset of values that are drawn in
func drawValues(context: CGContext). The problem is that the only option is to copy all code of this method from LineChartRenderer into my subclass, but there are warnings, because_xBoundsproperty has internal protection level.What did you expect to happen?
I would like to be able to control value position of DataSet entries on LineChart. For example, in LineChartRenderer in
func drawValues(context: CGContext)there is an alignment option, which is always set to.center, but I need to set it toleft.Also it would be great to change offset for X and Y position.
Is there any option to do that without making fork?
Charts Environment
**Charts version/Branch/Commit Number: 3.1.1 Release **
Xcode version: 9.3.1
Swift version: 4.1
Platform(s) running Charts: iOS
macOS version running Xcode: 10.13.4
The text was updated successfully, but these errors were encountered: