Hello Infragistics Team,
we have detected an Object Reference Exception in the Toolbar Version 8.2 CLR 2.0...
Is this a known issue?
at Infragistics.Win.UltraWinToolbars.RibbonGroup.PreventMouseInputNotification(UIElementInputType inputType)
at Infragistics.Win.UltraWinToolbars.RibbonGroupUIElement.WantsInputNotification(UIElementInputType inputType, Point point) at Infragistics.Win.UIElement.PointInElement(Point point, Boolean excludeOverlappingSiblings, Boolean ignoreClipping, Boolean honorInputType, UIElementInputType inputType) at Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings) at Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings) at Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings) at Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings) at Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings) at Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings) at Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings) at Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings) at Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType) at Infragistics.Win.UIElement.ElementFromPoint(Point point, UIElementInputType inputType) at Infragistics.Win.ControlUIElementBase.SyncMouseEntered(Boolean triggerMouseLeavesOnly, UIElementInputType inputType, Boolean ignoreLastElementEntered) at Infragistics.Win.ControlUIElementBase.ProcessVisibleChanged(Object sender, EventArgs e) at Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e) at Infragistics.Win.UltraControlBase.OnVisibleChanged(EventArgs e) at System.Windows.Forms.Control.OnParentVisibleChanged(EventArgs e) at System.Windows.Forms.Control.OnVisibleChanged(EventArgs e) at System.Windows.Forms.ScrollableControl.OnVisibleChanged(EventArgs e) at System.Windows.Forms.Form.OnVisibleChanged(EventArgs e) at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.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)
This post is 12 years old, and it does not appear that the original customer who reported it, or anyone else along the line, ever followed up and reported it directly to us, so it doesn't looks like it's ever been investigated.
From the call stack here, it appears that a RibbonGroup is becoming visible (or invisible) and the ToolbarsManager is trying to determine if it should be processing the mouse input notification. It does this in case it becomes visible (or is hidden) directly under the mouse so it can synch up whether it should be hot-tracked or not. Is your application using threads? This could be getting out of synch if your application is using multiple threads and not properly marshalling the data. I can't immediately see any case in which it should be blowing up, but the RibbonGroup in question is referencing it's own Ribbon and ToolbarsManager, so it's possible that there's a bug here. Is the call stack your users are getting exactly the same as the one listed here? It's tough to fix a problem we cannot reproduce, but I don't think it could hurt for us to put some null checks into this method to ensure it doesn't blow up.
Hello,
Are there any news / solutions / workarounds for this issue? Some clients of our software encounterd the same exception recently. Also infrequently as described above.
Regards
Thorsten
This happens infrequently and we are working on reliable reproduction steps. I have raised a support issue as well. Will report back when I have further details
It doesn't look like any fix was put in for this. Are you able to reproduce the issue consistently? Can you provide a sample or list of steps that would reproduce this issue?
We are seeing exactly the same crash in NetAdvantage 2010.2, did this issue get investigated?