This is a migrated thread and some comments may be shown as answers.

NumberFormatInfo in XAML

28 Answers 652 Views

NumericUpDown

This is a migrated thread and some comments may be shown as answers.

This question is locked. New answers and comments are not allowed.

28 Answers, 1 is accepted

answered on 01 Sep 2008, 02:19 PM

Hello Michael Hanson,

At the moment, Silverlight XAML parser throws an exception when trying to create NumberFormatInfo in XAML. We reported this to Microsoft.

When this is fixed, you will be able to set NumberFormatInfo in XAML in two ways:

1. Create NumberFormatInfo in page resources and reference it as a static resource:

    
            <UserControl x:Class="SilverlightNumericTest.Page" 
        
                xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"   
        
                xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" 
        
                xmlns:globalization="clr-namespace:System.Globalization;assembly=mscorlib" 
        
                xmlns:telerikInput="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls.Input">  
        
                <UserControl.Resources> 
        
                    <globalization:NumberFormatInfo x:Key="numberFormatInfo" NumberDecimalDigits="0"/>  
        
                </UserControl.Resources> 
        
                <Grid x:Name="LayoutRoot" Background="White">  
        
                    <telerikInput:RadNumericUpDown ValueFormat="Numeric" NumberFormatInfo="{StaticResource numberFormatInfo}"/>  
        
                </Grid> 
        
            </UserControl>

2. Create NumberFormatInfo and set it as an element value, like:

    
            <UserControl x:Class="SilverlightNumericTest.Page" 
        
                xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"   
        
                xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" 
        
                xmlns:globalization="clr-namespace:System.Globalization;assembly=mscorlib" 
        
                xmlns:telerikInput="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls.Input">  
        
                <Grid x:Name="LayoutRoot" Background="White">  
        
                    <telerikInput:RadNumericUpDown ValueFormat="Numeric">  
        
                        <telerikInput:RadNumericUpDown.NumberFormatInfo> 
        
                            <globalization:NumberFormatInfo NumberDecimalDigits="0"/>  
        
                        </telerikInput:RadNumericUpDown.NumberFormatInfo> 
        
                    </telerikInput:RadNumericUpDown> 
        
                </Grid> 
        
            </UserControl>

Greetings,
Hristo
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.

answered on 02 Dec 2008, 04:57 PM

I have this code from Hristo's sample:

    <UserControl.Resources>
        <globalization:NumberFormatInfo x:Key="numberFormatInfo" NumberDecimalDigits="0"/>
    </UserControl.Resources>
   <telerik:RadNumericUpDown VerticalAlignment="Center" NumberFormatInfo="{StaticResource numberFormatInfo}"      x:Name="TextBoxMonthsFreeOutsideTerm" Height="25" Width="50" LargeChange="1" SmallChange="1" Minimum="0" Maximum="12" ValueFormat="Numeric" />

This gives me AG_E_PARSER_BAD_TYPE at runtime. If I remove the NumberFormatInfo property from the control, everything works.

Are there plans to fix the bug anytime soon?

answered on 03 May 2009, 01:29 PM

I am having the exact same problems described here. As soon as you set the number of decimal places to zero the up/down arrows stop working.

The reply above talks about SmallIncrement but there is no such property. Assuming this was meant to say SmallChange this makes no difference.

I have a control on a page with the following style applied:

</Style>

The control itself is defined as follows:
<tki:RadNumericUpDown Grid.Row="1" Grid.Column="5" x:Name="RetirementIncomeUpDown" SmallChange="5000" LargeChange="10000" Style="{StaticResource NumericUpDownStyle}">

</tki:RadNumericUpDown>

Code behind sets the number of decimal places to 0:

var ud = (RadNumericUpDown)this.LayoutRoot.FindName("RetirementIncomeUpDown");

if (ud != null)

ud.NumberFormatInfo.CurrencyDecimalDigits = 0;

If I remove the code behind that sets the number of decimal digits the arrows are still broken. If I amend the range of values to more closely resemble those shown in the demo the down arrow works fine but the up arrow only works if I start with a negative value and even then only works up to the point the value reaches 0 (despite a maximum value of 100 being specified as allowable)

I'm very disappointed that what seemed like a fairly basic control (a) can't be initialised correctly in XAML to have no decimal places and (b) exhibits unpredictable behaviour when the arrow keys are used even when the decimal places are left to default to two places.

Are there any plans to supply fixes for these issues? On top of other issues (no documentation for some controls, limited functionality of the charting control, lack of support for anything other than images in the CoverFlow control etc) it is proving to be very hard to justify purchase of this set of controls once our trial evaluation period has expired, given our experience to date :-(

answered on 03 May 2009, 05:54 PM

Hi Ian,

Unfortunately both of these problems are part of the Silverlight framework. Creating your own style and setting it to a multiple numeric controls is a good practice to the extent that you save code. Unfortunately, the RangeBase class provided by the Silverlight Framework seems to have some problems with its coercing of Minimum and Maximum values when set in Style. I managed to reproduce your scenario and I noticed that if I set the Maximum property before the Minimum in the Style, the control works fine. To further prove my logic that the problem comes from the RangeBase class I created the same Style but for another control that also uses RangeBase - RadSlider. Declaring the Minimum property setter prior to the Maximum yields the same result - the RadSlider doesn't response to changing its value. That is a pity as I tested the issue in the Silverlight 3 implementation of RangeBase which appears to have the same problem.

What I would recommend is not to use Style, which will make your code a little bit more redundant, but will work correctly. For our next release we are planning to introduce our own RangeBase class that couples with generic types and hopefully doesn't introduce the same bugs as the Microsoft's one does.

Changing the NumberFormatInfo in xaml is still out of around hands. We will try to improve this formatting logic for our next release, and test whether an alternative one is required.

We pretty much understand the problem of not having a complete documentation at the moment, considering the load of support we experience. Improving our documentation is our next strategic goal. We will focus on gradually improving our documentation and online examples in order to meet the desired quality standards. I am sure you understand the trade-off between top-notch functionality and comprehensive documentation that requires extensive up to date revisions.

About the limitation of using only images in the CoverFlow. Silverlight 2, doesn't support perspective 3D transformation that will allow us to render any UI Element in perspective view. Fortunately, Silverlight 3 does support such transformation and the Silverlight team will stretch the framework capabilities to its maximum to deliver rich and reliable set of controls.

What I can say is that all of your experience is limited to the Silverlight itself instead of our controls. Microsoft has several essential cornerstones to achieve which are coming very soon. I hope this will answer some of your concerns and will help you make your final say in purchasing our controls. Stay tuned for the upcoming releases and always feel free to contact us for further assistance.

Greetings,
Hristo Borisov
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.