I'm trying to implement the locked feature of a Grid cell that's using a cell template.

I've found the Knowledge Base article that describes this scenario: Learn how to implement a locked column with a custom cell template inside the Native Grid but it doesn't work: not just in my implementation -- the demo doesn't work.

The ID cell in the demo should be locked, but isn't.

It may help if there was a documented list of the props available in a cell template somewhere, but I can't find one.

Any suggestions?

Hi Team,

          I was tried to custom render from Multiselect dropdown as a checkboxlist but while rendering I am getting the [Vue Warn]. Could you please help me to resolve the issue and help me out to get the checkbox list instead of multielect dropdown in the UI. Also please suggest the best practice to deal with this implementation. 

I have added the screenshot what I have tried with customItemRender method. Please guide me to achieve what I have tried for.

Thanks In advance.

Thanks

Gunasundari

I have just upgraded from version 5 to 6. Now the problem is that many types of events resolve to “(((...args: any[]) => void) | undefined”. In version <6, these were named events, which are also listed accordingly in the documentation. 
As a result, the projects can no longer be build. This also happens if version 6 is installed directly in an empty project.

Examples:

Are we doing something wrong here or are the type definitions incorrect?

Hello, 
I've upgraded my Kendo to version 6.0.1. and i has two warnings in console when using the component Editor.

`runtime-core.esm-bun…er.js?v=7677576e:50[Vue warn]: Methods property "onChange" is already defined in Props. at <KendoFontName view=undefined dir=undefined key=119 ... > at <KendoToolbar class="k-editor-toolbar" keyboardNavigation=true > at <KendoEditor key=0 ref="kendoEditorElement" value=.....`

and

` Methods property "onDown" is already defined in Props. 

`

Do you know the reason of  this warnings? 

Thanks advance. 

I can't seem to find anything in the docs about how to make the columns auto-fit the width of the container. In the grid wrapper, I've found https://docs.telerik.com/kendo-ui/knowledge-base/grid-autofit-all-columns-width and can use the dataBound event to access the autoFitColumn method. However, I just can't find anything similar in the docs for the native grid.

Thanks for any help I can get!!

How can you programatically change the height of the Grid?

My Grid is displayted within a container that can optionally switch to full-screen. The height of the Grid remains fixed, and applying a reactive style based on container height has no effect.

I'm setting both the initialWidth and initialHewight (600 and 400) to the Windows is large enough for the content, but it's not initially positioned at the center of the viewport when opened.

It displayed at the correct size, but it's too far to the right and too close to the bottom.

Any ideas why?

Hi, 

I am trying to evaluate the Vue Components but I cannot find any documentation about the data types. For example what is 

the data type of a scheduler item?

Is it still supported this product? Is it Typescript supported?

Every example looks really old using javascript and the options API and most of the links on the documentation are dead ...

Why are you allowed to tab focus onto the Month/Year selector at the top of the calendar control but cannot do the same with the DatePicker? With the DatePicker, focus is placed directly on the grid and only arrow keys work.  Is there some way to override this and tab onto the Month/Year selector?

There's no option for an Apply button on the Filter component.

The FilterChangeEvent fires with every action, so adding a new criteria triggers the event before the operator and values have been set.

If you've got the Filter hooked up to a Grid, this causes the rows to change in an unwanted way. This is particularly problematic if the data is coming from a remote API as it causes multiple GET requests, often with invalid filter configurations.

I can probably come up with a workaround that stores the value of the filter and only applies it when I click a button, but this shouldn't be necessary.