-
-
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
[feature request] enable legend view scrollable #151
Comments
Don't you prefer calculating how much dpace is needed for the legend and extending the view? |
usually the chart is centered, and the legend is at the bottom. If the legends are too many, finally it will go out of screen. If we extend the legend view, it either invade the chart's space, having some overlap, or some part of the legend is out of screen. |
What I do in an existing app is notifyDataSetChange() to tell it to On Tue, Jun 16, 2015 at 11:21 AM, Xuan notifications@github.com wrote:
|
if the legend height is very large, will the chart itself shrink its height? |
Yes. And you can control the "how much" through properties introduced lately |
@danielgindi I tested, the legend will horizontally expand if I have 5 or more legend items with out wrapping. If not support scrolling (which I think is the best way), consider support legend wrapping? |
There is legend wrapping currently for bottom legends, you just have to בתאריך יום שישי, 19 ביוני 2015, Xuan notifications@github.com כתב:
|
holy sht... I just saw wordWrapEnabled is in the middle of the code after I implemented my legend view with scroll view... |
Well we do not plan to support scrollable legends currently, as it is not a commonly required feature and not a good UX in most cases... |
I am not sure if the legend view is scrollable. I went through the code, but not found how can I enable it. If I have several legends and their label is long, it is better we can scroll the legend view to enable user can scroll on the legend. e.g. the legend view is a UIScrollView.
The text was updated successfully, but these errors were encountered: