We have a large winForms application that is using UltraGrid that is data-bound to a source.
A user that has utilized this form for many years has updated to a new computer. Since the update, the user is having an exception occur as they are using the TAB key to navigate through the form.
Are they any suggestions that I can get to help diagnose this situation?
The exception is
Error creating window handle.
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp) at System.Windows.Forms.Control.CreateHandle() at System.Windows.Forms.TextBoxBase.CreateHandle() at System.Windows.Forms.Control.RecreateHandleCore() at System.Windows.Forms.TextBox.set_CharacterCasing(CharacterCasing value) at Infragistics.Win.EmbeddableTextBox.Initialize(EmbeddableUIElementBase owningElement) at Infragistics.Win.EditorWithText.DisplayTextBox() at Infragistics.Win.EditorWithText.OnBeforeEnterEditMode(Boolean& cancel) at Infragistics.Win.EmbeddableEditorBase.EnterEditMode(EmbeddableUIElementBase embeddableElement) at Infragistics.Win.UltraWinGrid.UltraGridCell.EnterEditorIntoEditMode(Boolean byMouse) at Infragistics.Win.UltraWinGrid.UltraGridCell.EnterEditMode(Boolean byMouse, Boolean showingDropDown) at Infragistics.Win.UltraWinGrid.UltraGridCell.SetFocusAndActivate(Boolean byMouse, Boolean enterEditMode, Boolean byTabKey)
at Infragistics.Win.UltraWinGrid.UltraGridLayout.PerformAction(UltraGridAction actionCode, Boolean shiftKeyDown, Boolean ctlKeyDown)
at Infragistics.Win.UltraWinGrid.UltraGrid.PerformKeyAction(Enum actionCode, Boolean shiftKeyDown, Boolean ctlKeyDown)
at Infragistics.Win.ControlUIElementBase.ProcessKeyDown(Object sender, KeyEventArgs e) at Infragistics.Win.UltraWinGrid.UltraGridUIElement.ProcessKeyDown(KeyEventArgs e) at Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e) at Infragistics.Win.UltraControlBase.OnKeyDown(KeyEventArgs e) at System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m) at System.Windows.Forms.Control.WmKeyChar(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
thanks,
James
Hello James,
Looking at the call stack the issue is related to editor when its in edit mode. But not sure why changing the machine would cause this behavior?What environmental difference you made on this new machine?Did you change the version/build of infragistics control on this machine? Which version of control you are using?Are you not getting the same behavior for all the users? On other machines?
Are you getting this exception all the time when you tab?
I need more information to understand the nature of the issue.
the new computer is a newer Dell laptop model - I'm not sure of the hardware differences as our IT group is responsible for provisioning machines, but I do know that the dotnet version was both 4.8 for both pc's and the version of windows went from win10.0.16299(1709) to win10.0.19041(2004).
both pc's are 'on the domain' and the domain user configuration has not changed.
no changes to version of control during this time. running v19.1 (dll version 19.1.20191.379)
this is a new issue. No other users have reported the issue, and this particular issue did not encounter this issue until the new laptop.
the user has only reported the issue on this form and 'almost always' on a specific grid located on a tab panel. This is one column in that grid that we set the character casing to upper when the form is loaded. the exception does not occur all the time, but frequently enough to be annoying.
Let me know if you have further questions.
Changing the machine could not cause this unless you are using some old version on this machine.How did you transfer the dlls, were they in bin folder or you install the product on new machine.
If the issue is on one machine not on other than its hard to say , may be its running out of memory, Or having hardware issue, like a bad memory chip in that machine.
You mentioned that error is occurring when you are setting the CharacterCasing property on a Winforms TextBox. That causes the TextBoxes handle to get created, that's just what DotNet and Windows does, for whatever reason. So may be its's either multiple threading or a memory issue, which you have to investigate.
Regards,
Divya Jain
We are getting the same issue, is there any update on this issue