Hi, Team!
I would like to request an enhancement to the built-in drag selection functionality such that the Grid component is automatically scrolled thus allowing the user to reach rows and columns that are rendered on the page but are not currently visible.
When I type on a filter, the event filterChange is fired and it correctly contains the data of the column filter that has been modified, with its value.
The problem is that when a filter is cleared (either via clear button or by emptying the filter), the fired filterChange event does not contain any information. No name of the filter field is provided. This doesn't allow me to know which filter has been cleared.
It would be helpful to have a filter option inside the ColumnChooserComponent.
In some use cases we have around 30-50 items inside the list, it's hard to scroll through the small window to find your entries.
A simple textbox to search through the entries would be enough.
Hi,
It will be a good addition to the CheckboxColumnComponent if you allow developers to disable the checkboxes conditionally.
Workaround adding `k-disabled` class using class and headerClass properties:
https://stackblitz.com/edit/angular-n4gpjp-xqkpjz?file=src%2Fapp%2Fapp.component.ts
Hi,
It will be nice to have a feature to allow the Grid to be exported to Word(DOCX) format.
Hello,
In the documentation it says that sticky columns are not available while using virtual columns. It is really important for us to virtualize columns, when there's a lot of them in the grid, but also being able to use a sticky column at the same time.
Can you please consider implementing sticky columns while virtual columns are also enabled?
Best regards,
Boris
Hi,
Allow an option to filter when the user presses the enter key for the row filtering. The option can be a part of the StringFilterCellComponent(applicable to the other built-in filter components) and can also be considered for the TreeList component.
Hi, Team!
I would like to request functionality that would allow the developer to determine whether single or multiple items are expanded at the same time inside the Grid's Column Menu.
Currently, we can specify which columns to be included in the exported PDF file or Excel file:
It would be also convenient to have a property such as excludeFromPDF (or similar) for scenarios when only a single column should be removed from the PDF file.
Right now this is possible but defining the rest of the columns between <kendo-grid-pdf> tags which in scenarios with more columns drastically increases the HTML template.
Hi. We have a master-detail grid with the detail being a nested grid.
Unfortunately, as the master grid is scrolled, the detail grid header is scrolled out out of view, and the columns look odd because they do not match the master grid header.
Before scrolling:
After scrolling:
We would like to make the master row and detail header sticky.
Thanks.
Hi,
It will be a nice feature to have the ability to customize the drag hint of the built-in row reordering similar to the hintTemplate.
Please provide an option to configure the icon of the <kendo-grid-column-chooser> component. The available configurable options as input properties could be:
similar to the same input properties for the Button component:
https://www.telerik.com/kendo-angular-ui/components/buttons/api/ButtonComponent/
thank you
Highlight the text in the Grid with the filtered text. For example:
As there are browser-specific limitations to the maximum reliable height/width an HTML element can have (https://stackoverflow.com/questions/34931732/height-limitations-for-browser-vertical-scroll-bar), the virtual scrolling functionality of the Grid is affected (different issues appear depending on the browser).
It would be a nice enhancement to provide a way the virtual scrolling to work regardless of the total number of items in a given use case.
A possible solution is to keep track of a virtual window from 1 to 1,000,000 if the number of source records is greater than 1 million. On a scroll event, the scroll position can then be adjusted to reflect the position within the actual data set. For example, if the scroll position is 300,000 (within the max of 1,000,000) and the source data contains 50,000,000 records, the actual record index to start displaying data is 300000 / 1000000 * 50000000 = 15000000.
Workaround: