I'm using drawing.drawDOM to create a PDF. I have to make a table of contents in the beginning of the PDF. I've got two issues:
- How do I link to another section of the PDF? <a href="#conclusion">Conclusion</a> and then later <a name="conclusion"></a> doesn't seem to work :-/
- How do I figure out on which page a specific part of the document is being rendered? In my TOC I would like to say "Conclusion....page 22".
This is in reference to the following forum post:
For consistency in the MVC product, it would be a good idea to expose built-in events such as the "change" event for the generic Html.Kendo().TextBox helper. This is provided for other controls like the DateTimePicker and even NumericTextBox (https://demos.telerik.com/aspnet-mvc/numerictextbox/events) but not for TextBox.
As mentioned in my post, this is not an insurmountable problem. I can do what I need by diving "down" into jQuery, but it would be nice to be consistent.
Currently, when an event that is grouped by multiple resources is dragged, it automatically updates the selected resource data with the one that corresponds to the drop target.
The more appropriate behavior would be to be to automatically preposition the event for the rest of the selected resources.
When you export a sheet to Excel the Sheet is export as not-protected. If there are cells that are locked then the user can edit them. It would be really useful if you could specify tha a sheet were protected and when the sheet is exported it would be protected with a password.
Currently telerik MVC grid with DateTime column render datetime in local time zone. Nothing but if browser is accessing the site from CST time zone, grid automatically converting EST time to CST and shows value in CST. We have seen workaround as saving and showing data in UTC format. However this is not acceptable for some business scenarios. It’s better to have option to enforce grid to render date time as is input data. So that it will show consistent date time irrespective of local time zone.
Support for NullDisplayText property of the DisplayFormat metadata attribute.
When a user types 7/8/201x into a DatePicker, 7/8/201 is what ends up getting sent to the server. I believe an important function of a date-type-specific control or widget is to prevent the entry of bad data. The picker should not allow the entry of any string that is not a valid date or is outside of the Min-Max range (if specified). In fact, properly formatted dates typed into the textbox seem to ignore the Min-Max range. No user entering a date of birth is going to use the month selectors. He or she will type the date into the textbox. The datepicker, out of the box, should not allow the entry of invalid or out of range dates. The developer should not need to write a custom validator for behavior that virtually everyone would want.
Currently when a grid is bound to a model with related objects and properties via JSON, the grid will only parse the top level object types and treat and related properties as generic objects hence dates are not dates anymore, etc. Please consider having the grids parse related object properties and data types so there isn't a need for flattened ViewModels in order to properly visualize related data and be able to filter and sort it correctly.
The Kendo UI for MVC project template creates a blank test project. It would be nice if it had default code generated like the standard MVC project templates do.
Make it possible to use custom names for the unit test and OpenAccess projects while creating a new Kendo UI for MVC project.
Just like posted here (and declined) : http://kendoui-feedback.telerik.com/forums/127393-kendo-ui-feedback/suggestions/3844570-serialization-support-of-datasourcerequest-and-app I would like to see a portable separate assembly that : - can be referenced both on ASP.NET MVC side and WCF server side. - A DataSourceRequest and DataSourceResult class that serialize well in both SOAP and REST WCF. Referencing Kendo from the Application server side also requires references to System.Web.Mvc, Razor pages, ... and others that shouldn't be necessary.
We have a web page critical to the web application. In the absence of a suitable MVC widget we had to use a ASP.Net WebForm ListView control along with ASP.Net Ajax (Accordion for expand/collapse functionality) and JQuery (for client side validation). The web page accomplishes the following key functional requirements – a. Ability to group products – Using ASP.Net Ajax we were able to provide the expand / collapse visual effect. b. Ability to enter order quantities very quickly - a lot of stores place orders at the last minute (5-10 minutes before order deadline) for valid reasons. The web page provides a text box inline for quick entry. On a desktop, the user can traverse the rows within the group using the tab key. The web page typically contains 150 – 200 products for entry. With Telerik MVC Grid widget, in the absence of inline editing, having to click on Edit/Update/Cancel buttons dramatically increases the number of clicks / touch / swipe. Besides, it creates a real estate issue on smaller form factors. c. Real time validation – using JQuery we were able to validate the row as and when the quantity was entered. Any error would show below the row in question. The error would continue to show until the quantity was revised. The error however, will not stop the user from entering quantities on other rows. This approach lets the user review any errors in the end. The closest MVC widget we could use from the Telerik collection was the grid widget with grouping. However, it falls short on points b and c above. There is probably some workaround available but then we would lose the LOW CODE advantage.
Cancellation token is widely supported in entity framework. And it has big benefits for long running queries to allow cancel them. ToDataSourceResultAsync methods should support passing cancellation token as a parameter.
In order to fix concerns from #241 (https://github.com/telerik/kendo-ui-core/issues/241) the Autocomplete now shows a full list of items when the text entered has been deleted. This ignores the MinLength option, and can cause unresponsiveness in the browser (since MinLength is generally there to reduce the amount of results). From #574 this new functionality is intentional (and as such, the thread was closed as won't fix), but in practical terms, this causes issues for a lot of people. If you really don't want to enforce MinLength when 0 results are returned, perhaps adding an extraoption like 'AlwaysEnforceMinLength' would solve this problem