You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a DataGrid with MVVM-Binding and DataGridNumericUpDownColumn and DataGridTextColumn. A DataGridTextColumn can be edited directly, without pressing F2 or mouse double click.
A DataGridNumericUpDownColumn assumes to press F2 before I can edit.
Steps to reproduce
WPF-App with a DataGrid, a DataGridNumericUpDownColumn and DataGridTextColumn.
Navigate to the DataGridTextColumn
Type a number -> Cell will be edited
Navigate to the DataGridNumericUpDownColumn
Type a number -> Cell will not be edited
Easiest way to reproduce: MahApps.Metro.Demo-v2.4.10-rc0001
Expected behavior
The DataGridNumericUpDownColumn will be edited directly
Actual behavior
The DataGridNumericUpDownColumn will not be edited directly
Environment
MahApps.Metro version: v2.4.10
Windows build number: Win11 22H2 Build 22621.2428
Visual Studio: Community 2022 (64-Bit) - Version 17.7.5
Target Framework: .Net 7.0
The text was updated successfully, but these errors were encountered:
wannabe0815
changed the title
DataGridNumericUpDownColumn - Edit directly without F2
DataGridNumericUpDownColumn - Edit directly without pressing F2
Oct 20, 2023
Describe the bug
I'm using a DataGrid with MVVM-Binding and DataGridNumericUpDownColumn and DataGridTextColumn. A DataGridTextColumn can be edited directly, without pressing F2 or mouse double click.
A DataGridNumericUpDownColumn assumes to press F2 before I can edit.
Steps to reproduce
Easiest way to reproduce: MahApps.Metro.Demo-v2.4.10-rc0001
Expected behavior
The DataGridNumericUpDownColumn will be edited directly
Actual behavior
The DataGridNumericUpDownColumn will not be edited directly
Environment
MahApps.Metro version: v2.4.10
Windows build number: Win11 22H2 Build 22621.2428
Visual Studio: Community 2022 (64-Bit) - Version 17.7.5
Target Framework: .Net 7.0
The text was updated successfully, but these errors were encountered: