I received this crash notice from one of our customers when the calender portion of the UltraDateTimeEditor was visible and they were scrolling between months. What would cause this?
Normal 0 false false false EN-US X-NONE X-NONE System.ObjectDisposedException: Cannot access a disposed object. Object name: 'MonthDropDownWithUIPermissions'. at System.Windows.Forms.Control.CreateHandle() at System.Windows.Forms.MonthCalendar.CreateHandle() at System.Windows.Forms.Control.get_Handle() at System.Windows.Forms.Control.set_CaptureInternal(Boolean value) at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.MonthCalendar.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Here is a snippet from the screenshot taken at the time of the crash.
Hi,
What version are you using?
I can't find any records of an exception like this occurring, but my guess is that you are using a very old version of the controls and that this is an exception which was fixed a long time ago.
2010 Vol 1.
The assembly version of Infragistics2.Win.UltraWinEditors is 10.1.20101.1007.
thanks
Hello Jonhunt,
I believe that we have fixed similar issue in one of the service release for NetAdvantage 2010 vol.1 so if you could upgrade to the latest one available - 2105 this probably should be already fixed.
In order to download the service release, please log in to‘My IG’ and select ‘Keys & Downloads’. Select the appropriate tab for this product, then the license key. The available service releases should now be listed on the page.If you have any further questions with this matter please feel free to ask.
I'll try your suggestion, thank you.
Hello,
Thank you for your feedback.
Please feel free to let me know what are the results after you apply the latest service release to your application.
Since this was such a rare occurence (first time seeing it in over a year), it is not something I can replicate here unfortunately.
Also, I didn't see anything in the Service Release notes about any bug fixes related to this, so I don't think it will be solved. Thoughts?
Hello Jonhuntsynectic,
I am still following this forum thread.
Please feel free to let us know if you have any other questions with this matter.