ComboBoxCellType SingleCharacter search bug?

Posted by: overload-fp on 8 September 2017, 2:26 pm EST

  • Posted 8 September 2017, 2:26 pm EST


    I'm using the ComboBoxCellType with SingleCharacter search and whenever I try to traverse back up the list of items by just typing in the cell (do not open the drop down list), my application is crashing.  This appears to only be occurring if the ListControl is set.  If I just set the Items property, my application performs correctly.  For example, if I have 3 items in my ListControl (a, b, c), and I type 'a' in the cell, followed by 'b', and then type 'a' again, I receive a NullReferenceException with the stack trace shown below.  If I open up the drop down list before typing, I do not receive any errors.  I've attached a sample application.  Please let me know if I'm doing something incorrectly or if there is an issue with the ComboBoxCellType.  I'm using Spread Version=5.0.3511.2008.  Thanks.


         FarPoint.Win.dll!FarPoint.Win.FpCombo.a(int A_0, FarPoint.Win.AutoSearch A_1 = SingleCharacter) + 0x79c bytes   
         FarPoint.Win.dll!FarPoint.Win.FpCombo.WndProc(ref System.Windows.Forms.Message m = {msg=0x102 (WM_CHAR) hwnd=0x440b72 wparam=0x61 lparam=0x1e0001 result=0x0}) + 0x56 bytes   
         System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.OnMessage(ref System.Windows.Forms.Message m) Line 14059    C#
         System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.WndProc(ref System.Windows.Forms.Message m) Line 14114    C#
         System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.DebuggableCallback(System.IntPtr hWnd, int msg = 258, System.IntPtr wparam, System.IntPtr lparam) Line 777 + 0xa bytes    C#
         [Native to Managed Transition]   
         [Managed to Native Transition]   
         System.Windows.Forms.dll!System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(int dwComponentID, int reason = -1, int pvLoopData = 0) Line 2106 + 0x8 bytes    C#
         System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(int reason = -1, System.Windows.Forms.ApplicationContext context = {System.Windows.Forms.ApplicationContext}) Line 3377 + 0x1b bytes    C#
         System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoop(int reason, System.Windows.Forms.ApplicationContext context) Line 3261 + 0xa bytes    C#
         System.Windows.Forms.dll!System.Windows.Forms.Application.Run(System.Windows.Forms.Form mainForm) Line 1466    C#
    >    ComboBoxCellTypeTest.exe!ComboBoxCellTypeTest.Program.Main() Line 18 + 0x1d bytes    C#
         [Native to Managed Transition]   
         [Managed to Native Transition]   
         mscorlib.dll!System.AppDomain.ExecuteAssembly(string assemblyFile, System.Security.Policy.Evidence assemblySecurity, string[] args) + 0x3a bytes   
         Microsoft.VisualStudio.HostingProcess.Utilities.dll!Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly() + 0x2b bytes   
         mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object state) + 0x66 bytes   
         mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x6f bytes   
         mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x44 bytes   

  • Replied 8 September 2017, 2:26 pm EST


    I am able to replicate the issue at my end using the sample you have provide. I have reported it as a bug in Spread version 5.0.3511.2008 and 4.0.3522.2008 and the bug number for the same is <span id=":2fv">#99917738 which will be fixed in the future maintenance release of Spread.</span>


Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels