When changing the CurrentUICulture to a culture which requires comma as decimal separator (for example, German) - pressing the comma key does not work. You must press period. When pressing period "." -> "," is entered.

Currently, when you enter value directly in the input field, it is validated against Minimum and Maximum with every key stroke (on Value PropertyChanged).  This leads to some unexpected behavior as the Value is automatically updated to the min or max if it's not in their range. 

For example The minimum is set to 1000, but if i want to change the value via typing to 5000 you will see the issue, where it adds my new numbers on even after i have cleared the box

Currently, the only way to set the TextColor for the RadNumericInput is to extract the ControlTemplate and set the TextColor of the internal NumericInputEntry component.

A simple and quick fix is to add a TextColor BindableProperty to the RadNumericInput control and use a TemplateBinding on the NumericInputEntry style

Having a property in the control that could toggle decimal to whole numbers would be a good improvement to the control.

Hello,

It would be nice to be able to change the color of the NumericInput.

Please consider adding 2 bindable property : ButtonBorderColor and ButtonContentColor.

I can't use this control as it is. I had to create my own control.

It should be easy to implement IMHO.

 

Best regards

I've attached a sample solution to demonstrate the issue. Try to run it. There are two commands which change string format to currency and to percent  accordingly. So when you change string format by buttons on screen  it's not possible to see  it until  you tap on input 

I've attached a sample solution to demonstrate the issue. Try to run it.
When you run it you can see that it's not possible to see  value of numeric input until 
tapping on it  

RadNumericInput on UWP crashes as soon as you copy something and paste into the input. And it doesn't matter whether the copied text is numeric (12 for instance) or a text. I've attached a sample to demonstrate the issue.

If you modify the property which is bound to the Value of the RadNumericInput, through the ViewModel for example, you are able to set a value which is not in the range of minimum/maximum.