Declined
Last Updated: 26 Jul 2016 10:08 by Lisitsa
Add support for tooltip visualization over the continuous series segments that would interpolate the actual value between data points.

XAML Team reviewed this request and decided not to address it in the future. Appropriate way to get this is to use the crosshair behavior.
Declined
Last Updated: 26 Jul 2016 10:11 by ADMIN
Add support for tooltip visualization over the continuous series segments (besides the current support for visualizing the tooltip over the actual data point / point mark).

Declined due to duplication with http://feedback.telerik.com/Project/143/Feedback/Details/113405-chartview-enhanced-tooltip-support-for-continuous-series-segments-line-area-e
Completed
Last Updated: 06 Oct 2015 08:01 by Chetan
Knowing where the cursor is and the associated coordinate and data information is critical to really create highly functional finacial chart. It allows the developer to overlay order tools on the chart like trendlines, possibly even enables the end-user to place an order directly from chart.

- Enhance cartesian chart interactivity by enabling the usage of TrackballInfo features without actually showing the trackball e.g. show the OHLC info in the top left corner of the chart (add mouse down/move events as well).
- Enable scenarios that need to pass trackball info to other charts e.g. on chart #1 you want to show trackball info for chart #2 at the same time (knowing the trackball info and coordinates of each chart is critical to syncing the track info of another chart that may be below the main chart as stock would want to see the tracking info for all chart simultaneaously).

Available in Q2 2015 Release.
Declined
Last Updated: 26 Jul 2016 10:40 by MikeWiese
ADMIN
Created by: Telerik Admin
Comments: 1
Category: ChartView
Type: Feature Request
8
When SnapMode=TrackBallSnapMode.None the IntersectionPoints should be drawn not over DataPoints but over the real intersection between series and TrackBallLine (also the TrackBallControl should display the real calculated intersection value itself).

XAML Team reviewed this request and decided not to address it in the future.