Page 1 of 1

ZoomTool on Webchart while using Hotspot-Tool at the same ti

Posted: Mon Oct 27, 2008 1:42 pm
by 10549438
Hello,

I'm trying to use the ZoomTool of a "Webchart" (with 7 gantt-Series) while having the HotSpot-Tool enabled. The HotSpot-Tool's property "MapAction" is set to "Script" to show some more information in a Pie-Chart on the MouseOver-Event.
When I enabled the "zoomTool" to my "Webchart", the HotSpot-Tool is not working any more. Is there any posibility to get this working?

Thanks.

Best Regard
Michael

Posted: Mon Oct 27, 2008 2:10 pm
by narcis
Hello Michael,

Yes, this is possible. I just sent you an example where both features work together.

Posted: Mon Oct 27, 2008 3:28 pm
by 10549438
Hello Narcís,

Thanks for the example-code. I've added this to my Website, but it's quite not working. When I enable the "ZoomTool", the HotSpot is not working. Where have I to place the call for

Code: Select all

seriesHotSpot1.GetHTMLMap += new Steema.TeeChart.Tools.SeriesHotspotEventHandler(seriesHotSpot1_GetHTMLMap);
?

Best regards.
Michael

Posted: Mon Oct 27, 2008 4:07 pm
by narcis
Hi Michael,

You need to reassign the event after loading the template chart. I sent you the updated version of the example.

Hope this helps!

Posted: Tue Oct 28, 2008 7:56 am
by 10549438
Hello Narcís,

thanks for the code-example.
I've tried to get both features working together with the new code. When I set the SeriesHotspot-Property "MapAction" to Mark or URL it's working how it should.

With MapAction set to "Script" it's not working correctly.
I wrote a script which is similar to the "DrillDown"-example on your website. When the user does a "MouseOver" a Series, there is a small rectangle with some other series in a Chart shown. This works just fine until I enable the zoom Tool. With ZoomTool is enabled, the Chart with the additional Series does not appear on the Screen on a mouseOver-Event.

Thanks

Best Regards
Michael

Posted: Tue Oct 28, 2008 8:44 am
by narcis
Hello Michael,

Thanks for the information. I've been able to reproduce the issue here and added it (TF02013491) to the defect list to be fixed for next releases.