I have a wpf datagrid bound to a TrackableCollection. In some rare occations, and for only a few selected users, the application will crash when the user adds a new record by entering the bottom blank row. I have not been able to reproduce the issue, and all I have is a stacktrace of the exception thrown. Has anyone seen anything like this? I have limited knowledge about the automationpeer-classes, but I can confirm that we are not using any of them in our application.
Here's the stacktrace:
System.ArgumentNullException: Value cannot be null.
Parameter name: item
at System.Windows.Automation.Peers.DataGridAutomationPeer.CreateItemAutomationPeer(Object item)
at System.Windows.Automation.Peers.ItemsControlAutomationPeer.FindOrCreateItemAutomationPeer(Object item)
at System.Windows.Automation.Peers.DataGridAutomationPeer.RaiseAutomationSelectionEvents(SelectionChangedEventArgs e)
at System.Windows.Controls.DataGrid.OnSelectionChanged(SelectionChangedEventArgs e)
at System.Windows.Controls.Primitives.Selector.SelectionChanger.End()
at System.Windows.Controls.DataGrid.MakeFullRowSelection(Object dataItem, Boolean allowsExtendSelect, Boolean allowsMinimalSelect)
at System.Windows.Controls.DataGrid.HandleSelectionForCellInput(DataGridCell cell, Boolean startDragging, Boolean allowsExtendSelect, Boolean allowsMinimalSelect)
at System.Windows.Controls.DataGridCell.OnAnyMouseLeftButtonDown(MouseButtonEventArgs 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.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
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.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, 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)
XAML:
<DataGrid Name="OrdreSLinjeGrid"
AutoGenerateColumns="False"
CanUserResizeRows="False"
CanUserAddRows="{Binding KanLeggeTilOrdreLinjer}"
HorizontalScrollBarVisibility="Disabled"
VerticalScrollBarVisibility="Visible"
ItemsSource="{Binding Order.OrderLines, Mode=TwoWay}" CanUserSortColumns="False"
SelectedItem="{Binding ValgtOrdreLinje}" >
<DataGrid.Columns>
<DataGridTextColumn
Header="{t:Translate Antall}"
TextAlignment="Right"
Width="50"
HeaderStyle="{StaticResource HøyrejustertColumnHeader}"
Binding="{Binding Antall, UpdateSourceTrigger=LostFocus}" />
<DataGridTextColumn
Header="{t:Translate Pris}"
Width="60"
HeaderStyle="{StaticResource HøyrejustertColumnHeader}"
Binding="{Binding Pris, UpdateSourceTrigger=LostFocus, ValidatesOnDataErrors=True}"
/>
</DataGrid.Columns>
</DataGrid>
Any input or suggestions will be appreciated.
I have the same issue. It occurs on Datagrid when user double clicks first row in DataGrid (with only one row). This is occurs only on Sony laptop with touchscreen. Sony software adds checkboxes to every file in Winfows Explorer. I think this problem is related to the sony software.
The problem is related to a bug in
DataGridAutomationPeer.RaiseAutomationSelectionEvents
internal method which simply speaking does not check if SelectedItem property is null or not. It can easily be reproduced by running "Microsoft Narrator" tool in Windows 7.Because this is a sealed class there is no easy way to fix it except intercepting this method using Reflection.Emit or any mocking tool out there and even if it's fixed we have no guarantee that Microsoft won't change this method name, signature or behaviour.
I implemented a "good enough" fix by inheriting from DataGrid which will change the way DataGrid is unselected when the SelectedItem is null but only if narrator/touchscreen is present.
Hopefully the bug will be fixed soon. Add reference to UIAutomationProvider if necessary.
I would try to check for nulls on your properties in your view model. If the property is null, replace the null with a valid value like a 0 or a blank.
You could also do this using a Value Converter
No need for converters or for using a derived class. Just make sure that the property you are binding to for SelectedItem is initialized with DependencyProperty.UnsetValue. Do not set it to or leave it at the default of null.
The underlying bug should be fixed in the not-too-far future, btw: https://developercommunity.visualstudio.com/content/problem/575165/vs-1604-ide-crash-argumentnullexception.html
I had the same issue with touch screen only. I had a WPF app that was working fine until I connected the touch screen that the app was built for.
This issue occur when the DataGrid selected item was bounded to an object that was null;
I resolved it this way:
The DataGrid Xaml had this line:
The XVVM looked like:
I know this is pretty old, but there is a good solution to this problem that I came across. You can define a custom converter using the
IValueConverter
interface:This checks if the value is
null
and if it is, returnsDependecyProperty.UnsetValue
. As described in the documentation (look at the method descriptions):Returning this rather than
null
should fix the issue.