DataBinding broken in NumericUpDown in .Net4 version

6 posts, 0 answers
  1. Peter Chapman
    Peter Chapman avatar
    17 posts
    Member since:
    May 2010

    Posted 24 Nov 2010 Link to this post

    Dear Telerik,

    I've updated our application to the .Net 4 version or Q3 WPF, i'm using the trial whilst the full version is being purchased. (2010.3.1119.40)

    Our app was built using Q1 2010. 

    I've updated the assemblies, and now the databinding for telerik controls has stopped working.  Lets say I have a view model with a bunch of properties, half of which are bound to telerik controls, and half of which are bound to standard controls. They are all bound to update their source on PropertyChanged. The standard controls still update their view model property, but the telerik controls do not.

    help!

    thanks
    Pete
  2. George
    Admin
    George avatar
    1332 posts

    Posted 26 Nov 2010 Link to this post

    Hello Peter,

    Thank you for contacting us.

    Could you please specify which databindings are broken? If you send us a running sample project that reproduces the problem it would be very helpful in further pinpointing the problem.  I will be glad to assist you further.

    Regards,
    George
    the Telerik team
    Browse the videos here>> to help you get started with RadControls for WPF
  3. UI for WPF is Visual Studio 2017 Ready
  4. Peter Chapman
    Peter Chapman avatar
    17 posts
    Member since:
    May 2010

    Posted 02 Dec 2010 Link to this post

    George,

    i can't attach a project here, so i'll submit a support ticket.

    thanks
    Pete
  5. Peter Chapman
    Peter Chapman avatar
    17 posts
    Member since:
    May 2010

    Posted 05 Jan 2011 Link to this post

    If anyone else has this problem, it is a bug. There is no fix scheduled.

    Telerik's reply was: 

    'There is a problem when the default value of NumberValueProperty and the RadNumericUpDown.Minimum are equal. I would suggest you to set a diferent Minimum for the RadNumericUpDown control - for example 0. 

    You can track this progress in our Public Issue Tracking System (PITS) with Issue ID = 4266.'

    The workaround was of no use to us, we needed the default value and the minimum value to be the same. We made out own numericupdown instead.


  6. deepak
    deepak avatar
    25 posts
    Member since:
    Jan 2011

    Posted 18 Jun 2011 Link to this post

    As i change the value of NumericUpDown using buttons, binding of value property to another element breaks.
  7. Konstantina
    Admin
    Konstantina avatar
    2332 posts

    Posted 23 Jun 2011 Link to this post

    Hello Deepak,

    I tried to reproduce the issue, but to no avail. Could you please prepare a sample project in which this can be observed and send it back to us. In that way we will be able to track down the source of the problem.

    Looking forward to your reply.

    Kind regards,
    Konstantina
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top
UI for WPF is Visual Studio 2017 Ready