#DEFINE VtChPartTypeChart 0 && Part type - chart #DEFINE VtChPartTypeTitle 1 && Part type - title #DEFINE VtChPartTypeFootnote 2 && Part type - footnote #DEFINE VtChPartTypeLegend 3 && Part type - legend #DEFINE VtChPartTypePlot 4 && Part type - plot #DEFINE VtChPartTypeSeries 5 && Part type - series #DEFINE VtChPartTypeSeriesLabel 6 && Part type - series label #DEFINE VtChPartTypePoint 7 && Part type - point #DEFINE VtChPartTypePointLabel 8 && Part type - point label #DEFINE VtChPartTypeAxis 9 && Part type - axis #DEFINE VtChPartTypeAxisLabel 10 && Part type - axislabel #DEFINE VtChPartTypeAxisTitle 11 && Part type - axistitle #DEFINE VtChPartTypeSeriesName 12 && Part type - series name #DEFINE VtChPartTypePointName 13 && Part type - point name #DEFINE VtChPartTypeCount 14 && Number of elements in this enumeration object.TwipsToChartPart(nX, nY, @iPart, @iIndex1, @iIndex2, @iIndex3, @iIndex4) DO CASE CASE WHEN iPart = VtChPartTypeChart ... ENDCASE>In MSChart, there is a function called TwipsToChartPart. The ruler has been solved. But the TwipsToChartPart is killing me. My expectation was that it would behave as "Hittest" does in Treeview or Listview), and that a mousemove "across" a series datapoint
TwipsToChartPart(x, y, iPart, iIndex1, iIndex2, iIndex3, iIndex4)>
TwipsToChartPart( nX,nY,.f.,.f.,.f.,.f.)
.caption=transform(TwipsToChartPart(x, y, iPart, iIndex1, iIndex2, iIndex3, iIndex4)>