This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi Jason, I am setting the DisplayMemberBinding property for a datagrid column with UpdateSourceTrigger=UpdateSourceTrigger.LostFocus When I modify the value in a datagrid cell it causes my property changed event to be fired immediately rather than just when we lose focus of the cell (it actually almost appears to be losing focus on its own). As a result I can only type a single letter at a time before it kicks me out of the datagrid cell and executes some code. I am not able to type out a full string in the datagrid cell as a result. Please help. Thanks. |
|
|
|
|
Hello Kamal Thanks for pointing this out. This will be resolved in the next nightly build. Jason Fauchelle |
|
|
|
|
HI Jason, I downloaded Aug 01, 2013 nightly build. You fix this problem but created new crashes, please see the exception caught below. System.NullReferenceException: Object reference not set to an instance of an object. at Mindscape.WpfElements.WpfDataGrid.DataGridRow.GetCell(DataGridColumn column) at Mindscape.WpfElements.DataGrid.#U7(DataGridCell cell) at Mindscape.WpfElements.DataGrid.#W7() at Mindscape.WpfElements.DataGrid.OnLostKeyboardFocus(KeyboardFocusChangedEventArgs e) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Input.KeyboardDevice.ChangeFocus(DependencyObject focus, Int32 timestamp) at System.Windows.Input.InputManager.RaiseProcessInputEventHandlers(ProcessInputEventHandler postProcessInput, ProcessInputEventArgs processInputEventArgs) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input) at System.Windows.Interop.HwndKeyboardInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawKeyboardActions actions, Int32 scanCode, Boolean isExtendedKey, Boolean isSystemKey, Int32 virtualKey) at System.Windows.Interop.HwndKeyboardInputProvider.PossiblyDeactivate(IntPtr hwndFocus) at System.Windows.Interop.HwndKeyboardInputProvider.FilterMessage(IntPtr hwnd, WindowMessage message, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) Thanks, Gordon |
|
|
|
|
Hello Gordon Thanks for pointing this out. It doesn't look like this is related to any of the code changes I made yesterday though. This will be resolved in the next nightly build and will not be able to occur again. Jason Fauchelle |
|
|
|
