#Datagrip copy with headers code#

When querying different data with the same column names, this can lead to unintended results.I am using the C1DataGrid Component. While using templates for auto-generated columns is useful, the templates are applied based on the column name. See _grid_AutoGeneratingColumn in the sample application for non-templated auto generated columns. You can set this context menu in various ways, when using auto-generated columns directly on the TextBox in the template, or using a style. In order to catch the event, you can use a custom ContextMenu like shown below: The TextBox inside the DataGridCell uses TextEditorContextMenu.OnContextMenuOpening, which prevents you from receiving the events. In order to detect whether a context menu is open, you can use the ContextMenuOpening and ContextMenuClosing events. In the CellEditEnding event, you cancel the event when a context menu is open. The solution is based on WPF DataGrid Sample: Locking input to the row being edited. The reason for this is that when opening the context menu, the focus changes and the DataGridCell goes out of edit modus. When you right click on a TextBox in edit mode, the context menu is shown, but the items are disabled, which prevents you from using it. While using the DataGrid, I noticed that the context menu of the TextBox was not working correctly in edit modus. TextBox context menu in DataGrid edit modus

#Datagrip copy with headers code#

The code therefore was based on the code found in the links listed below: To make the sample application a bit more useful, code to allow the user to copy the data from the DataGrid to the clipboard is included. For example, a template is used for showing clickable links. Running this query will show columns where templates are used.

The AutoGenerateColumn class is listed below: AutoGenerateColumnCollection is a class that extends ObservableCollection and is used to store the column names and templates. The AutoGenerateColumnCollection originates from the attached property GenerateTemplateColumn.Columns. TemplateColumn.SortMemberPath = e.Column.SortMemberPath TemplateColumn.CellEditingTemplate = col.CellEditingTemplate TemplateColumn.CellTemplate = col.CellTemplate Object sender, DataGridAutoGeneratingColumnEventArgs e)ĪutoGenerateColumnCollection coll = GetColumns(grid) ĬustomDataGridTemplateColumn templateColumn = In this event handler, a new DataGridTemplateColumn column is created when the current column name is found in the AutoGenerateColumnCollection.Ĭopy Code public static void _grid_AutoGeneratingColumn( The AutoGeneratingColumn event handler is listed below. In order to reuse data templates for multiple fields, I created a custom class, CustomDataGridTemplateColumn, that extends DataGridTemplateColumn and adds binding support. The data context for DataGridTemplateColumn is DataRowView. This column has no binding support like DataGridBoundColumn. There is already a column class with support for templates, called DataGridTemplateColumn. By setting DataGridAutoGeneratingColumnEventArgs.Column, you can provide your own column. You can adjust or cancel the generated column in the event handler. This event is fired for each individual column that is generated. The DataGrid provides an event called AutoGeneratingColumn. This article shows how you can use a DataTemplate for automatically generated columns with an attached property. While this is quite useful, it does not give much control about the generated column. Setting AutoGenerateColumns to true will automatically generate a column for each field. The DataGrid is a control for displaying tabular data.