Home Forums WinForms controls Xceed Grid for WinForms Need help with this exception

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • User (Old forums)
    Member
    Post count: 23064
    #15504 |

    Hi,

    We saw this exception in the field. I am trying to reproduce the same problem in house.

    Exception: Exception has been thrown by the target of an invocation.
    Stack Trace: at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess)
    at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean verifyAccess)
    at System.Delegate.DynamicInvokeImpl(Object[] args)
    at System.MulticastDelegate.DynamicInvokeImpl(Object[] args)
    at Xceed.Grid.GridElement.RaiseEvent(Object eventKey, EventArgs e)
    at Xceed.Grid.VisualGridElement.OnMouseDown(MouseEventArgs e)
    at Xceed.Grid.Cell.OnMouseDown(MouseEventArgs e)
    at Xceed.Grid.GridControl.DoMouseDown(MouseEventArgs e)
    at Xceed.Grid.GridControl.OnMouseDown(MouseEventArgs e)
    at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at Xceed.Grid.GridControl.WndProc(Message& m)
    at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    It looks like it is happening at the MouseDown event. I do call the Invalidate() event within the OnMouseDown event.

    I am trying to put more debugging in that code, meanwhile can any one point me what could be the cause of this.

    Much Thanks.

    Imported from legacy forums. Posted by kushaljn (had 2366 views)

    User (Old forums)
    Member
    Post count: 23064

    The only thing you can conclude from this is that an exception occured in the MouseDown event handler. To get the actual exception that happened, you should check the InnerException property of this exception.

    Imported from legacy forums. Posted by Tommy (had 326 views)

    User (Old forums)
    Member
    Post count: 23064

    From the looks of that stack trace,

    I’d say some delegate is being attached to the MouseDown event that doesnt have the right parameters or parameter type. So when the delegation is happening, it fails.

    Might be wrong though.

    Imported from legacy forums. Posted by DarkByte (had 3516 views)

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.