RadDateTimePicker input error

6 posts, 0 answers
  1. Sheena
    Sheena avatar
    3 posts
    Member since:
    Jul 2013

    Posted 23 Jul 2013 Link to this post

    Hello,

    I'm getting this error if i try to input "9999/12/31 24:00".
    System.ArgumentOutOfRangeException: The added or subtracted value results in an un-representable DateTime.
    Parameter name: value

    This doesn't happen the first time. The first time, it just changes to 12:00 which is okay. On re-input, I get the above error. Somehow the control throws this error and I can't catch this even in the viewModel.
  2. Kalin
    Admin
    Kalin avatar
    1208 posts

    Posted 24 Jul 2013 Link to this post

    Hello Sheena,

    Thank you for reporting this issue, we managed to reproduce and it has been logged it in our P.I.T.S. system. You can track its status on the following link:
    http://www.telerik.com/support/pits.aspx#/public/wpf/15425

    I have updated your Telerik points for your involvement as well.

    Regards,
    Kalin
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  3. UI for WPF is Visual Studio 2017 Ready
  4. Sheena
    Sheena avatar
    3 posts
    Member since:
    Jul 2013

    Posted 30 Jul 2013 Link to this post

    Hello,

    I'd also like to report on a minimal bug for RadDateTimePicker also. When I input "23:" without the double quotes in the time, it changes to 11:00 AM in the hints.. "23" shows 11:00 PM but when adding the colon character, it changes back to AM.

    Just a thought, any possible estimate for the fix for the previous bug?
  5. Rosen Vladimirov
    Admin
    Rosen Vladimirov avatar
    640 posts

    Posted 02 Aug 2013 Link to this post

    Hello Sheena,

    Thanks for reporting the second problem. We have already found it and in fact we are working on it. You can track its status here. We'll do our best to include both of the fixes in one of our internal builds, but I'm not able to give you exact timeframe.

    We are sorry for the caused inconvenience. Feel free to contact us in case you have any problems or concerns.

    Regards,
    Rosen Vladimirov
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  6. Sheena
    Sheena avatar
    3 posts
    Member since:
    Jul 2013

    Posted 30 Aug 2013 Link to this post

    Hello,

    Regarding the first issue, I know this is still being fixed on. But are there other similar issues that we should be aware of? Just so we can create a workaround for our side.
  7. Rosen Vladimirov
    Admin
    Rosen Vladimirov avatar
    640 posts

    Posted 03 Sep 2013 Link to this post

    Hello Sheena,

    We are currently working on some fixes and hopefully we'll be able to include them in our next official release. 

    We are sorry for the caused inconvenience. Feel free to contact us in case you have any problems or concerns.

    Regards,
    Rosen Vladimirov
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
Back to Top
UI for WPF is Visual Studio 2017 Ready