I use an UltraTree in OutlookExpress StyleView.
With a name, value Column set, i add an EditorWithCombo to the value cell (DataType is string)
The EditorWithCombo use a class dervied by DefaultEditorOwner to fill the EditorWithCombo with a ValueList, that contains Enum Values.
Everything is displayed correctly, but when i select an item from list, following exception occurs:
Additional information: Object reference not set to an instance of an object.Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object. at Infragistics.Win.ValueList.Infragistics.Win.IValueList.CloseUp() at Infragistics.Win.EditorWithCombo.DoCloseUp() at Infragistics.Win.EmbeddableEditorBase.CloseUp() at Infragistics.Win.EditorWithCombo.Infragistics.Win.IValueListOwner.OnCloseUp() at Infragistics.Win.ValueListDropDown.OnCloseUp(Boolean closeDropDownManager) at Infragistics.Win.ValueListDropDown.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at Infragistics.Win.ValueListDropDownUnsafe.WndProc(Message& message) at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.ComponentManager.System.Windows.Forms.UnsafeNativeMethods+IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.Run(Form mainForm)
I am using Infragistics version: 6.3.20063.1059
I would download the latest hotfix to see if the issue has been resolved; I think that the final hotfix version for 6.3 is 1091. If this issue still persists, you should contact Developer Support, but keep in mind that 6.3 is no longer actively maintained, meaning that the earliest version that a fix would be applied to is 7.2.
-Matt
Hi Matt
I got the same problem in 9.1 as well
Regards,
Stephen