We have a legacy product that is using UtlraWinSchedule 6.3.20063.53, specifically UltraMonthViewSingle + UltraWeekView + UltraCalendarLook with ViewStyle = Office2007, and it suddenly started throwing the following exception when any appointment is hovered over twice in either MonthView or WeekView:
System.OverflowException: Arithmetic operation resulted in an overflow. at Infragistics.Win.ImageManager.InteropBitmapData..ctor(Bitmap bitmap, ImageLockMode lockMode, PixelFormat pixelFormat) at Infragistics.Win.ImageManager.CreateBitmapRegionInterop(Bitmap bitmap, Color transparentColor) at Infragistics.Win.ImageManager.CreateBitmapRegion(Bitmap bitmap, Color transparentColor) at Infragistics.Win.ImageRegion.CreateShapeRegion() at Infragistics.Win.ImageRegion.get_Region() at Infragistics.Win.ToolTipMetrics.GetToolTipRegion() at Infragistics.Win.ToolTip.ShowNoActivate() at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
We have the .TipStyleActivity property set to 'None', but with ViewStyle = Office2007 this setting appears to be ignored and the tooltip is displayed anyway. The first time the appointment is hovered over, the tooltip displays without error. The second time any appointment is hovered over is when the exception occurs. This exception does not occur when ViewStyle is set to anything other than Office2007 (no tooltip is displayed).
I realize this is an ancient product, and this is probably related to some sort of .NET Framework/Windows update, but it's happening on several of our clients machines including my dev box (Windows 10 64bit). I am reaching out in desperation of a solution. Is there any way we can either swallow the exception and prevent it from crashing the application, or prevent the tooltip from displaying in the first place for ViewStyle=Office2007?
My team and I have done an initial review of this forum thread, and the exception that you are seeing sounds like it could be something that may be coming from usage of a 64-bit process to run your application. As such, I am curious if running your application in a 32-bit process would resolve the issue here. I would recommend trying this, and you can see how to force your application into a 32-bit process at this article.
It is also interesting that setting the TipStyleActivity property to “None” is not working. It is possible that this could have been a bug in that the Office2007 ViewStyle that is overriding the TipStyleActivity, but I am unsure at the moment. I would be more curious to see if the 32-bit operation works for the time being.
Please let me know if you have any other questions or concerns on this matter.
Sincerely, Andrew Goldenbaum Software Developer
Great suggestion - setting the target to x86 fixed the problem. Thank you for taking the time to answer.