Hi, is there a way i can customize the paging options style? The default is we have the page selection on the left, number of Items per page selection in the middle and the total records info on the right. I would like to just reverse it. I tried a display flex on the container and a flex-direction: reverse but it reverses the paging icons also. Please advise.
A custom render method for the paging component or a wrapper around the paging buttons would be ideal so as to do a flex-reverse to play around with the styles.
Typing 111 in DatePicker results in skipping the day part. The third 1 is set to the year portion.
It is reproduced in our demo as well:
https://www.telerik.com/kendo-react-ui/components/dateinputs/datepicker/
};
<Grid
}}
<Column field="Date"filter="date"format="{0:d}"/>
In this way,the date will be sorting with Month, How can I sorting start with year instead of month
The KendoReact Tooltip component only displays tooltips on hover (the showTooltip method is called on the onMouseOver and onMouseLeave events). It would be ideal if the showTooltip method was also called on the onFocus event as well, making the user experience the same for keyboard-only users.
Most other UI libraries treat hover/focus the same for consistency and accessibility.
Bootstrap requires it:
https://getbootstrap.com/docs/4.1/components/tooltips/#making-tooltips-work-for-keyboard-and-assistive-technology-users
Material UI allows you to disable focus interaction, but the default is that focus is handled the same as hover:
https://material-ui.com/api/tooltip/#props
I discovered a lack of parity between the React and Angular implementations of the TabStrip/TabStripTab components. Specifically, in the React version the "title" prop determines the contents inside the resulting <k-link> CSS class, whereas the Angular version allows you to set a template, for more complex tab header components.
This became an issue for me, because we have overridden the CSS for a custom progress tracker component built on the tab strip in an Angular implementation. I am now tasked with replicating the component in React, but had to resort to my own TabStrip/TabStripTab classes, instead of being able to use your components. (My goal is to be able to use the existing CSS, maintained by our UX team, out of the box.)
Hope that made sense. Feel free to contact me if it's not clear what I'm asking for, or if there is already a solution to this. Thanks!
React version:
Angular Version:
I want to make a request to add the autoClose property to manage KendoReactMultiSelect control.
Here is an example of code with several MultiSelect controls on the same page without the autoClose property:
https://stackblitz.com/edit/react-w4yhvh
You can clearly see that the autoClose property will be really useful.
Thanks.
It would be great to have a TreeList component similar in appearance and behavior to the jQuery TreeList (https://demos.telerik.com/kendo-ui/treelist/index), but with the kind of support for virtual scrolling built into the native KendoReact Grid component.
A React wrapper exists for the jQuery TreeList, but it still doesn't play nicely with React, and in any case only supports paging for displaying large data sets, which is inherently not intuitive for displaying tree structures where parent / child hierarchies might span multiple pages.
My sense is this native component would basically be the Grid, but with support for hierarchical data, including drag-and-drop re-ordering of parent / child relationships.
Thanks for considering this feature.
Like in the jQuery counterpart, when I click on a cell to edit the value - I should be able to tab over to the next cell to edit it.
We are evaluating the React Grid component for our application and need to be able to have rows that span all columns. To do this, I have created a rowRender function that, for some rows, will render a single <td> element with the colspan set to 100%. The row renders fine, but the other rows, that have multiple <td> elements do not all render correctly. For my test application, they will render with a width of 8 pxs. On resize of a column, they will almost render correctly.
Here are some pictures of the issue in our test code.
https://drive.google.com/open?id=1bMwlUi7-7QiVHc6lubPiz45svHG1FSnS
I have created a sandbox that sort of reproduces the bug. https://codesandbox.io/s/w73v0x0mz8
If you select the "Show Full Row", the row with Id 999 will convert to a single <td> element with colspan='100%'. You will notice how after doing so, the last three columns collapse to a small number of pixels.
Thanks
Joe
If you create a react grid without any GridColumn components and then add those components later, the added columns do not show and the grid is empty. It appears, after a quick look that the columns have a width of 0 pixels. They exist in the html, just not displayed.
See https://codesandbox.io/s/mmr894nllp as an example of the problem. This example starts with a populated grid. You can add columns and data using the buttons above the grid. This works fine. If you then "Reset" the grid with the button, which removes all data, any attempt to add columns and data will show a blank grid.
Thanks,
Joe
Multi-selecting rows using the mouse selection doesn't work for React Kendo Grid.
With the kendo grid wrapper for React we were able to multi-select rows using the mouse selection in the grid bounds.
We have database constraints on certain fields e.g. varchar(10) and would like to prevent the user from entering invalid data into the combo box fields. If it's not too much trouble a minLength field would also be convenient.
I'd like to be able to get the generated pdf data from GridPDFExport in a callback, instead of saving to file. This is useful for emailing pdfs. It can easily be achieved by adding a 'generatePDF' method to the KendoDrawingAdapter prototype such as this: KendoDrawingAdapter.prototype.generatePDF = function (callback) { var _this = this; var savePromise = this.drawDOM(this.domElement, this.getDrawOptions()) .then(function (group) { return _this.exportPDF(group, _this.getPDFOptions()); }) .then(function (dataUri) { return dataUri }); if (callback) { savePromise.then(callback, callback); } };
Grids should have auto width and max-width property