Bug: SelectableDateStart not adhered to upon entry

[Kevin]

If I set the SelectableDateStart to be say '10/27/2010', I cannot select a date earlier to this but I can type one in (example 10/26/2010).

[George]

Hello Kevin,

Thank you for contacting us.

We are aware of this behavior of RadDateTimePicker and this is its default behavior. It's logged as feature request in our Public Issue Tracking System (PITS) and you can affect its priority by voting for it. The more clients' requests we receive the sooner we'll include it in our development plans. You can track this progress in our PITS with Issue ID = 2911.

Please do not hesitate to contact us if you require any further information.

Kind regards,
George
the Telerik team

[Kevin]

If I do not want a user to be able to select a date prior to a certain one, why would I want them to be able to manually enter one?  I do not see how this default behavior is justified.  Perhaps you can suggest a scenario where this is the desired functionality?

[Tyree]

I agree with Kevin. Sure we can add code behind when the value changes and test if its between the selectable dates but not sure why we have to.

[George]

Hello Tyree,

If we receive more common clients' requests we will include it in our further release.

All the best,
George
the Telerik team

[Jeffrey]

I too am complaining. It's very frustrating when you include properties that are supposed to alter functionality and they do nothing.  

[Kaloyan]

Hello Tyree,

We are aware of the particular lack of functionality and  trying to resolve it as early as possible.

Greetings,
Kaloyan
the Telerik team

[Tyree]

Is this in Q1?

[Kaloyan]

Hi Tyree,

We haven't managed to include the fix in the Q1 bits. Hope it will be ready for some of the upcoming service packs. Please accept our apologies once again.

All the best,
Kaloyan
the Telerik team

[Adam]

This is still not fixed?

DisplayDateStart="{Binding Path=Today}" SelectableDateStart="{Binding Path=Today}"

[Yana]

Hello Adam,

I am afraid that this fix was delayed due to more urgent tasks. At the moment we cannot specify a timeframe for implementing this change.  We are sorry for the inconvenience.

I would suggest to use ParseDateTimeValue event to check the entered in the input date.

Greetings,
Yana
the Telerik team

[Steven]

Any idea when this bug might be fixed? It really doesn't make sense to have keyboard entered dates ignore the selectable date criteria.

[Steven]

I wrote the following attached behavior to fix the problem with keyboard entered dates. 

Just set RadDateTimePicker.KeyableDateStart and/or RadDateTimePicker.KeyableDateEnd

To customize the error message - set ErrorTooltipContent to your own custom message.

/// <summary>
/// Adds ability to restrict the text entered date of a RadDateTimePicker or RadDatePicker.
/// </summary>
public static class RadDateTimePicker
{
    public static DateTime? GetKeyableDateStart(DependencyObject sender)
    {
        return (DateTime?) sender.GetValue(KeyableDateStartProperty);
    }

    public static void SetKeyableDateStart(DependencyObject sender, DateTime? value)
    {
        sender.SetValue(KeyableDateStartProperty, value);
    }

    public static DateTime? GetKeyableDateEnd(DependencyObject sender)
    {
        return (DateTime?) sender.GetValue(KeyableDateEndProperty);
    }

    public static void SetKeyableDateEnd(DependencyObject sender, DateTime? value)
    {
        sender.SetValue(KeyableDateEndProperty, value);
    }

    private static void OnKeyableDateChanged(DependencyObject sender, DependencyPropertyChangedEventArgs e)
    {
        if (e.OldValue == e.NewValue)
            return;

        var datePicker = sender as Telerik.Windows.Controls.RadDateTimePicker;
        if (datePicker == null)
            return;

        datePicker.ParseDateTimeValue -= OnParseDateTimeValue;
        datePicker.ParseDateTimeValue += OnParseDateTimeValue;
    }

    private static void OnParseDateTimeValue(object sender, ParseDateTimeEventArgs e)
    {
        var datePicker = sender as Telerik.Windows.Controls.RadDateTimePicker;
        if (datePicker == null)
            return;

        var startDate = GetKeyableDateStart(datePicker);
        if (startDate != null && e.Result < startDate)
            e.IsParsingSuccessful = false;

        var endDate = GetKeyableDateEnd(datePicker);
        if (endDate != null && e.Result > endDate)
            e.IsParsingSuccessful = false;
    }

    public static readonly DependencyProperty KeyableDateStartProperty = DependencyProperty.RegisterAttached("KeyableDateStart", typeof(DateTime?), typeof(RadDateTimePicker), new PropertyMetadata(OnKeyableDateChanged));

    public static readonly DependencyProperty KeyableDateEndProperty = DependencyProperty.RegisterAttached("KeyableDateEnd", typeof(DateTime?), typeof(RadDateTimePicker), new PropertyMetadata(OnKeyableDateChanged));
}

[Alexander]

Bug is also present when DateSelectionMode.Month or DateSelectionMode.Year is used.

[Kiti]

Is this bug fixed??

I need to implement the same feature in my project. Can you please give an update?

[Yana]

Hello Kiti,

This feature is still not implemented, you can track its progress and vote in our PITS here.

Also I would suggest to check this Code Library  for a possible solution how to restrict the entered in the DateTimePicker date.

I hope this helps.

Regards,
Yana
Telerik