Colorline tool drag event issue

BenW · Post by **BenW** » Fri Jan 18, 2008 1:04 am

Hello.

I have created a line chart with a single yaxis. I've associated with the chart and yaxis, 2 distinct ColorLine tools, the first representing a high threshold and the second representing a low threshold. I have subscribed to the EndDragLine event on both ColorLine instances and each is calling a distinct handler.

When I drag the Colorline representing the high threshold, both EndDragLine event handlers (i.e. even the one for the ColorLine representing the low threshold) are being invoked??

This is undesirable in my implementation as the subscribers to these events need to be able to process them independently and distinctly.

Can you cofirm if this is an internal Steema issue, and what may be done as a work around?

thanks!
Ben.

Narcís · Post by **Narcís** » Fri Jan 18, 2008 9:47 am

Hello Ben,

I haven't been able to reproduce the problem here using latest TeeChart for .NET v3 maintenance release available at the client area, which is Build 3.2.2930.22968. Which TeeChart version are you using?

Thanks in advance.

BenW · Post by **BenW** » Fri Jan 18, 2008 5:23 pm

Hi Narcís,

I hope 2008 is treating you well so far...

... I don't really know the specific version number, as we have built our Teechart.dll from a version of Steema source code that is likely at least 1 yr old, but it is TeeChart for .NET v2 and a version prior to 2.0.2887.28039/50...

thanks,
Ben.

Narcís · Post by **Narcís** » Mon Jan 21, 2008 10:40 am

Hi Ben,

I hope 2008 is treating you well so far...

Thanks. Yes, 2008 is being good for now. I hope you had a good start and continues better.

... I don't really know the specific version number, as we have built our Teechart.dll from a version of Steema source code that is likely at least 1 yr old, but it is TeeChart for .NET v2 and a version prior to 2.0.2887.28039/50...

Thanks for the information. I've been able to reproduce the issue here using v2 and checked that already works fine in v3. I've added the defect (TF02012749) to our bug-list to be considered for inclusion in possible new v2 updates. There's no workaround I can think of at the moment.

BenW · Post by **BenW** » Mon Jan 21, 2008 3:06 pm

Hi Narcís,

Thanks for confirming that it is an issue...

Regards,
Ben.