Currently, when setting the value property of the TimePickerComponent programmatically (without using two-way binding in the template), the control does not update its displayed value until it gains focus. This behavior is inconsistent, especially when compared to other controls that properly reflect programmatic value changes.

Example - https://stackblitz.com/edit/angular-nhg2x1b9-d7f5bhh9?file=src%2Fapp%2Fapp.component.ts

template: `
     
      <kendo-timepicker
        #timepicker
        format="HH:mm:ss" 
      ></kendo-timepicker>
      <kendo-datetimepicker  #datepicker></kendo-datetimepicker>
     <kendo-dateinput #dateinput></kendo-dateinput> 
   
  `,
})
export class AppComponent {
  public value: Date = null;
  @ViewChild(TimePickerComponent) private kendoControl: TimePickerComponent;
  @ViewChild('dateinput') private dateinput: DateInputComponent;
  @ViewChild('datepicker') private datepicker: DateInputComponent;
  constructor(private cdr: ChangeDetectorRef) {}
  ngAfterViewInit() {
    this.kendoControl.value = new Date();
    this.dateinput.value = new Date();
    this.datepicker.value = new Date();

    this.cdr.markForCheck();
    this.cdr.detectChanges();
  }

hi,

We would really appreciate RTL support for our Hebrew customers for KendoDateinputs.

The current behavior is VERY confusing for users and causes them to input the wrong data for both date and time components, causing them to lose critical information.

 Thank you!

Thanks,

Shahar

Please provide an option that would allow to disable multiple time ranges for the TimePicker component, so that a time isn't possible to be selected from these disabled time ranges.

thanks