Hello,
I have an UltraCombo with AutoCompleteMode = SuggestAppend. It's drop down contains a list of predefined forms. When I use the mouse and click on any value in the drop down, there is no error in launching/loading the chosen form. However, when I use a keyboard to type in the form name, we get the error Can't access SelectionStart unless the Editor is in edit mode. At trace, I can see that all of my code was already finished. It was able to get the form name and launch the form. However, just before it gives control back to the user, the error occurs.
Please help. Stack Trace below. Thanks.
StackTrace " at Infragistics.Win.EmbeddableEditorBase.get_SelectionStart()\r\n at Infragistics.Win.EmbeddableEditorBase.set_SelectionStart(Int32 value)\r\n at Infragistics.Win.EditorWithCombo.ProcessAutoComplete(Keys lastKeyDown)\r\n at Infragistics.Win.EditorWithCombo.ProcessTextBoxTextChanged(Boolean& selectionChangedByAutoEdit)\r\n at Infragistics.Win.EditorWithCombo.Infragistics.Win.IEmbeddableTextBoxListener.OnTextChanged()\r\n at Infragistics.Win.EmbeddableTextBox.OnTextChanged(EventArgs e)\r\n at System.Windows.Forms.TextBoxBase.WmReflectCommand(Message& m)\r\n at System.Windows.Forms.TextBoxBase.WndProc(Message& m)\r\n at System.Windows.Forms.TextBox.WndProc(Message& m)\r\n at Infragistics.Win.EmbeddableTextBoxWithUIPermissions.WndProc(Message& m)\r\n at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)\r\n at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)\r\n at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)\r\n at System.Windows.Forms.UnsafeNativeMethods.SendMessage(HandleRef hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)\r\n at System.Windows.Forms.Control.SendMessage(Int32 msg, IntPtr wparam, IntPtr lparam)\r\n at System.Windows.Forms.Control.ReflectMessageInternal(IntPtr hWnd, Message& m)\r\n at System.Windows.Forms.Control.WmCommand(Message& m)\r\n at System.Windows.Forms.Control.WndProc(Message& m)\r\n at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)\r\n at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)\r\n at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)\r\n at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)\r\n at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)\r\n at System.Windows.Forms.Control.DefWndProc(Message& m)\r\n at System.Windows.Forms.Control.WmKeyChar(Message& m)\r\n at System.Windows.Forms.Control.WndProc(Message& m)\r\n at System.Windows.Forms.TextBoxBase.WndProc(Message& m)\r\n at System.Windows.Forms.TextBox.WndProc(Message& m)\r\n at Infragistics.Win.EmbeddableTextBoxWithUIPermissions.WndProc(Message& m)\r\n at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)\r\n at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)\r\n at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)\r\n at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)\r\n at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)\r\n at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)\r\n at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)\r\n at System.Windows.Forms.Application.Run(Form mainForm)\r\n at CTRL_pad.Classes.clsProgram.Main() in C:\\CTRLPAD Server\\CTRLPAD Windows Application\\CTRLPAD Development\\Classes\\clsProgram.cs:line 16" string
What's the status of this issue? I'm having the same problem.
Hi,
In that case, I'm not sure what's wrong. Can you duplicate this in a small sample project so we can check it out?
Hi Mike, we were using v2009.1. I have just updated to v2009.2 but the error is still occuring. Please help. Thanks!
My guess is that this is a known issue that is already fixed. Make sure you have the latest service release:
How to get the latest service release - Infragistics Community