If you take a look to the provided screenshot you'll see what's wrong at first sight.
If you add a numeric input belong other kind of input.
You will see that the numeric input is the only one control to have a style which look like the control is being focused.
the NumericInput color is using the accent color for all states. We can't guess whether the control is focused or not.
the numeric input should have a default color and use the accent color only when focused. Use the default entry style for the entry of the numeric input.
you can also expose a numericButtonStyle property or some bindable property to allow us to set the color.
Right now, the control is unusable because of its look. Too bad, the implementation behind is nice.
It was better to create my own control which does the same. I use Telerik to avoid that.
Have a good day and thanks for your attention.
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.
1. If there is "0" and you are trying to add "." (dot) after it - it doesn't allow you to do this (droid and iOS) 2. Start input from "." and you will see cursor before dot, not after it as usually is happening (droid only) 3. Start input ".0" and it changes to "0", if I want to get number e.g. 0.09 (droid and iOS) Available in minor release 2018.3.1122. It will also be available in the R1 2019 release.
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
Steps to reproduce 1. Run the solution on UWP 2. When main page is loaded tap "Next Page" 3. Put the cursor focus onto the numeric input field 4. Without losing the focus tap back button 5. Application crashes Available in minor release 2018.2.821. It will also be available in the R3 2018 release.
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.
Samsung numeric keyboards insert minus sign after the second stroke of a multi-functional button. This restricts Samsung end users to directly insert minus in the RadNumericInput because the control reacts on the beforehand entered decimal separator. We should improve our logic in order to handle this type of input. Available in the 2018 R2 SP release.
Available in the R2 2018 release.
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.