Hi Team,
I'd like to request adding the Buddhist Calendar to the Kendo UI Date/Time Pickers/Calendar.
Thank you!
Date picker when entering the day or day and month to autofill the content with current year or current month and year, same as asp.net ajax datepicker
Dear support,
I didn't find in your documentation if and how we can use data-* annotations to setup dataInput options of a datepicker.
I would like to do the same thing that the code below does but with MVVM data-* annotation.
self.date= $('#dateExample').kendoDatePicker({ format: 'dd.MM.yyyy', dateInput: true, }).data('kendoDatePicker'); self.date._dateInput.setOptions({ format: 'dd.MM.yyyy', messages: { 'year': 'yyyy', 'month': 'mm', 'day': 'dd' }
I globally use data-bind for html and kendo UI components.
I just added the data-format in my html like below, and it works.
<input data-role="datepicker" id="dateExample" data-format="dd.MM.yyyy" data-bind="value: myValue">
I wonder if we can setup format and messages options for the dateinput of the datepicker with MVVM without using jquery (with something like data-dateinput, data-dateinput-format, data-dateinput-messages...).
Thanks in advance for your usual support.
Regards,
Charline.
It would be great to allow custom configuration of Time drop down in DateTimePicker control. Since most occurrences in normal system will take place between normal business hours (7am - 6pm), it would make sense to have the time dropdown start at 7am and then go on from there so it would be: 7am 8am 9am .... 4pm 5pm 6pm ...... 12am 1am etc. This would improve user experience by putting the most commonly selected times first in the dropdown list and reduce the scrolling the user has to perform.
Hi Team,
I would like the user to be able to add a value into the Kendo UI DateTimePicker's input with the calendar opened. Currently, if the calendar is open, the focus will be on the calendar, and it will select today's date upon pressing enter.
Thank you!
Optionally allow for the disabling of Daylight Savings time detection when using the DateTime picker, or to set the TimeZone for the picker manually.
Globalized applications use the DateTimeOffset type instead of DateTime since it includes the offset from UTC for different time zones. If DateTimePicker could bind to this type it would simplify UI development. It would have to have the offset or timezone value provided as either a property or as a second binding.
It is essential that k-ng-model integrate completely and accurately with angular. For instance if I am using k-ng-model with a date picker and set it to required angular validation will not work. This same issue exists with all of the kendo controls that support k-ng-model
Would like Timepicker that works the same as your Windows Forms Timepicker, with a SpinEditor.
Hello,
I would like to request adding a property like DisplayDate which will select the view and value of the Kendo UI DatePicker initially without setting it with the value method.
Thanks!
Instead of a drop down for the time choices can they be displayed so the user doesn't have to scroll through a drop down and the choices can be displayed similar to your example on UI for WinForms. Thanks.
It would be helpful if when entering a date into a datepicker control you could just type +7 to have it select 7 days from today. Or -5 for 5 days ago. Or if you just type 0, it would select today. Or type 15 and it would select the 15th of the current month. This would make keying in dates much faster than using the calendar.
Is there any possibility to add a new property to the datepicker that will let the user to use a datepicker like the ones used in materializecss framework? Sample here: http://materializecss.com/forms.html#date-picker
The datepicker does not validate the year when selecting a date and prepending the year with a number. However if you put any character after the year it is stripped off. It would be understandable to allow dates that are longer than 4 digits but the picker only goes to 2099. This causes the date to be returned as null.
Currently when creating a Date/Time Picker object by using the time in milliseconds since 01.01.1970 UTC the Date/Time Picker works perfect. When trying to submit a form containing a Date/Time Picker, the widget will submit the formatted time/date instead of the milliseconds since 01.01.1970 UTC. There is a workaround to extend the onChange Event and manipulate the value of the input field manually. This might solve the technical problem but now the UTC milliseconds will be displayed inside the widget. Might it be possible that the widget formats the display date/time and keeps a hidden input field for storing the value? It is actually not possbile to use dates/times in UTC milliseconds with this widget allthough the JavaScript Date object can handle it.
In a filter input field I had one blur event to fix a entered date string. It wasn't called if the users hit "Enter" instead of cliking the Filter button or hitting TAB which would cause a blur event. T. Tsonev asked me to post this to "UserVoice portal": Maybe an event that is triggered before attempting to read the value from the input. This will consolidate both handlers in your case. Below are the two handlers to fix an input field if a blur or Enter key is done/hit: --- If an input field is changed and the user does a blur (TAB or clicks filter button) after entering a date or hits the enter key without doing a blur. the FixDate function is called and input field is changed before the filter popup is submitted and the Filter works if a date like this is entered: 11/9/2004 0:0 FixDate canges to: 11/9/2004 12:00 AM. Below is the code I changed: See the sections with "Fix " comments. Maybe they need a on "blurOrEnter" event so you don’t need to make two tests? (((, or an event that is triggered before attempting to read the value from the input))) ... // Fix - Modified to call a FixDate function. // Test for a blur (ie: click or tab to another widget and leave the input field) // NOTE: blur doesn't happen when the enter key is hit $("[data-role=datetimepicker]").on("blur", function() { var element = $(this); FixDate(element); }); // Fix - Modified to handle the "Enter" key // and call the FixDate function // to modify the input field from "11/9/2004 0:0" to 11/9/2004 12:00 AM" // before the form is submitted. // This makes the filter work when the enter key is hit // which doesn't cause a blur to happen. $("[data-role=datetimepicker]").on("keydown", function(e) { // Test for Enter key if (e.keyCode == 13) { var element = $(this); FixDate(element); } }); } }); // Change the date in the filter input field by using // Datej Date.parse. // This will change strings like: "0:0" // To: "1/29/2015 12:00 AM" // and allow the filter to work function FixDate(element) { // Get element for datetimepicker //var element = $(this); // Get widget for datetimepicker var widget = element.data("kendoDateTimePicker"); // See if element has changed if (element.val()) { // Set Text of widget to a Datejs string date from the elements text // IE: 11/9/2004 0.0 will be 11/9/2004 12:00 AM widget.value(Date.parse(element.val())); // Fix by T. Tsonev 01/26/2015 // make a change happend so new text is used. // ie: Use "11/9/2004 12:00 AM" instead of "11/9/2004 0:0" widget.trigger("change"); } } ... ---
The current date time and date-time pickers don't allow for scrolling the data using the mouse scroll. This functionality is available in ajax controls this makes a mix web site not consistent in behavior of controls.
DatePicker should let developer decide if the chosen day of the month should be persisted from month-to-month. By default the DatePicker remembers the day of the month the user has selected, and that day gets styled differently even when the user navigates away to a different month: the user selects January 12th and then navigates to August, and the 12th day of August is styled differently too. But there are many use cases for a DatePicker where it is not appropriate behavior to remember the previously selected day of the month when the user navigates to a different month. Remembering the day can actually make things confusing for the user in applications where this behavior is not the right behavior.