Hi,
I've been working on an application containg a WinChart Pie3D control and am encountering a problem where the tooltips of the pie segments are placed a few hundred pixels from the top and left of the mouse cursor.
Searching for a solution I found a reference to bug 34946 whis was fixed somewhere in 9.2 while I am using 10.3.
After much searching I found that this bug manifests itself when:
The chart is contained in a docked panelThat panel is contained in an Mdi ClientThe Mdi Client top left location is not (0,0) within its Mdi parent form
I created a small project in VS2010 which recreates the bug, and could upload it when desired.
TIA,
Wim
see following post, gives a workaround
http://blogs.infragistics.com/forums/p/59749/314885.aspx#314885
Hello Colin
The mentioned issue was fixed a long time ago. I try to reproduce this issue using the latest version, but without success. If you are able to reproduce this issue in a sample, please send us this sample. I`ll be glad to research it.
Thanks in advance and I`ll wait your response !
I am also having this same problem.This is on a non mdi form. the tooltip seems to be appearing by an offset equal to the width of the docked panel to the left of the chart. If I resize this width, the tooltip distance changes accordingly. I am using 10.3 winforms, but have tried upgrading to 11.2 - does not fix it. I've seen many forum posts that complain about flavours of this, but they all seem to come down to the same issue I think. I've spent ages trying to make a sample that exhibits this bug, but I can't for whatever reason, it only happens on my app, so it must be a combination of factors, which I can't seem to pin down. Also I see that infragistics personal keep saying it is a bug that was resolved already, but I've tried the latest version, and it still is a problem.
Cheers
Colin
I understand. Is it possible to send us a small sample (or a single page), in which this issue is reproducing, so we can investigate it asap.
I applied the September service pack before I posted, given that earlier in this thread it was mentioned that you had fixed a similar issue to the previous poster. It still does not work.