You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the ChartViewDelegate method chartValueSelected is tied up with Highlights, meaning it fires when you highlight a bar and doesn't fire when you de-highlight a bar (instead, chartValueNothingSelected is called). That's great, but when highlightEnabled is set to false, neither method fires when a bar is tapped. It would be awesome if these two could be untangled in that situation - if highlightEnabled is false, tapping the bar should always fire chartViewSelected, just like it's a simple tap gesture recognizer.
The text was updated successfully, but these errors were encountered:
maybe some format for your text.. hard to read.
It depends on different needs. Some people thought highlightEnabled is false should not trigger any highlight behavior at all..
you are the first to ask this.
Maybe a second flag then, to decouple the tap gesture recognizer from the highlighter? Having a tap gesture recognizer that just fires on all taps feels more like a standard iOS API, it would be great to have this.
chartViewSelected is not a tap recognizer. If you want a UITapGestureRecognizer, then add one. chartViewSelected is not fired when there's no selection, because there's no selection, I think it's plain English and it makes sense...
I noticed that the ChartViewDelegate method
chartValueSelected
is tied up with Highlights, meaning it fires when you highlight a bar and doesn't fire when you de-highlight a bar (instead,chartValueNothingSelected
is called). That's great, but whenhighlightEnabled
is set to false, neither method fires when a bar is tapped. It would be awesome if these two could be untangled in that situation - ifhighlightEnabled
is false, tapping the bar should always firechartViewSelected
, just like it's a simple tap gesture recognizer.The text was updated successfully, but these errors were encountered: