If an UltraWinChart is disposed of and removed from a form, that chart may throw an unhandled NullReferenceException when the form repaints.
The IGWinTooltip class of an UltraWinChart registers for the top level form's Paint event, but doesn't unregister when the IGWinTooltip is disposed of. This causes the IGWinTooltip to handle the Paint event of the form while it's in a disposed state. While the IGWinTooltip is in a disposed state, it attempts to reference a private memeber that was set to null in its Dispose() implementation.
Can anyone at Infragistics confirm this and give some idea as to when this might be fixed? I've worked around the issue by overriding my form's OnPaint event and hiding the exception.
-Mike
Will give that a go.
Many Thanks,Scott.
if there were breaking changes between those versions, they would be documented here: http://help.infragistics.com/NetAdvantage/WinForms/2010.3/CLR2.0/?page=Win_Known_Issues_and_Breaking_Changes.html
but there weren't any breaking changes recorded for WinChart or WinGauge. you should be able to update to the latest version (11.2) painlessly. there's always a chance of some broken compatibility, but your chances are good that it will go smoothly. i suggest you download the trial version of NetAdvantage for Windows Forms 2011 Volume 2 and see what happens when you update the references and run your project.
as for the cost of upgrade, please contact Infragistics Sales for this information (http://es.infragistics.com/about-us/contact-us.aspx#ContactUs).
Hi David,
Thanks for the quick response :-)
I am coming at this fairly cold, so wondered if you could point me in the right direction for answers to the following:
Is there any documentation covering the upgrade path from 2007 to 2008? (I believe we are currently using UltraWinGauge and UltraWinChart)
What would the cost be for this upgrade?
The earliest version it was fixed in is 2008 Volume 1.
Hi,
We are seeing this issue on: Infragistics NetAdvantage 2007 Vol. 1 CLR 2.0
Can anyone tell me what HotFix or Version contains a fix for this?