I have a jquery mobile app that I'm converting to kendo-ui mobile.   It uses forms inside of collapsible's extensively.  Kendo UI doesn't like it.  I tested by copying the example mobile collapsible  index.html from examples to my app, works fine.  Then tried pasting various example mobile-forms.  They all fail, the page is a mess.

I guess I'll have to figure another way unless you guys have some solution?

I’ve just started using your PDF-generation library and so far I am very pleased with the results. I have a couple of features I would love to see implemented though:

Keep-together: The page-splitting seems to work very well, but sometimes you have elements which you would prefer not to be split. Of course if this element is too large for a page, it should still be split. I would love to be able to have the possibility of using a class to indicate that an element should be entirely moved to the next page instead of splitting, unless it is already at the top of a page.

Scaling: While I don’t agree with your decision to treat px as pt (they are very clearly defined to be respectively 1/96 and 1/72 of an inch), at least your documentation on the issue is great. To get around it, I’ve used css-scaling, which seems to work fine. I do, however, encounter some issues with clipping on absolutely positioned elements, mainly headers/footers, but nothing I havn’t been able to solve. But it would be great if scaling was built into the API, it would solve the px/pt problem completely and might be useful in other scenarios where the rendered size should be different from print-size. Simply including “scale: 0.75” as a draw-dom option and then upscaling page-size and down-scaling all calculated sizes and positions in the output seems like it should be possible.

First page margin: This should be rather simple, but would be very useful I think. Often you don’t want as much info in the header of the first page, as it will include the title and subtitle of the document. If you could specify the margin for the first page separately, you could better handle this.

Headers on split tables: Splitting a table across multiple pages works great, but has one problem: the table header will only be shown on the first page (and presumably the footer will stay on the last page). There are two problems with this: firstly, showing the header on the second page will make the table much more usable for the reader. Secondly, the header often has column width directly applied to it. This width is not copied when split, so the second-page columns will be automatically sized. I realize this might be quite complicated and could probably also raise more problems, like how to indicate to the user that this is a split table, but I imagine many people would find it useful.

Force black/white only: I’ve run into an issue when trying to print a table with every other row highlighted in a slight blue-gray (background #f3f4f8, border #eaebef). This looks great in the browser and in the PDF, but when printed both the stribes and the borders are almost invisible. This is most likely a problem with the printer, but might just as well be a problem in a customers printer. Printing as B/W resolves the issue, so being able to force all colors to be converted would be great. “filter:grayscale(100%)” doesn’t seem to be respected (I suspect because computed styles are not affected by this).

Hopefully some or all of these could be possible to implement at some point. Otherwise, keep up the good work :)

I've created a demo page in JSfiddle, where you can see I've tried to use the number format and filterable to do the filtering for a numeric column. But if the data is suppose 0.23252 and my format condition "{0:n3}" and in filterable if I use the below function then the filtering is not working anymore. Please help. 

{
                ui: function (element) {
                    element.kendoNumericTextBox({
                        format: "n3",
                        decimals: 3
                    });
                }
 }

 http://jsfiddle.net/5EHqL/71/

Thanks,

Megha

Hello there,

Recently I was working on the MultiSelect control, because we can select a lot of items from the drop down list, so in the tags container it will display these tags in several rows. I know there are two modes to render the tags, single and multiple, but we just want use multiple and if there are more than 5 selected items, we just render 5, then add an additional button such as "more" at the end of these selected tags.

There are tag template and item template to render customize style, but there is not a container template we can change.

how to implement this?

How do you add a custom tooltip for specific columns in the grid?
For example, one my columns has the following grid schema setting:

When there is no value entered, the error message in the tooltip is "item1Description is required". How can I make it show a custom description like "Item 1 Description is required"?

I have a Angular grid setup with locked columns (so there are scrolling), resizable = true, and fixed column width. However, occasionally the content is longer than the column width. I want to programmatically call autoFitColumn() method to make the columns to fit the content. I don't see any event to signal grid render complete. Where is a good place to call autoFitColumn()?

I tried dataBound event, but I use template with angular expression in it. At point of dataBound, the angular expression are not evaluated yet, so the calling autoFitColumn in this event will actually make things worse.

Best,

Ama

Hello,

I've few problems with Kendo UI diagram control in my Angular 1.4 project. In my case I use diagram to draw an organization chart from the top to the bottom.

1. Is it possible to customize connectors (output) behavior to be drawn always from the the bottom (see attachment)? Now I've a badlook situation that connectors output random from every side.

2. How to restrict the pan/scroll area to not to move the diagram outside current viewport.

3. I want to load diagram `kendoDiagram(this.kendoDiagramOptions)` asynchronously by $q (Angular Promise) or rxjs. When I simply put this to the promise, diagram initialization seems to block whole application until its done. How to bypass this behavior.

Best regards.