I have a Xamarin.Forms app, but I only am using it for UWP at the moment. The plan is to have Android and iOS later, but I am having issues with the RadNumericInput (Xamarin.Forms) and how the decimal key is handled.
Here is my XAML
<tkInput:RadNumericInput Grid.Row="4" Grid.Column="1" Value="{Binding Price, Mode=TwoWay}" StringFormat="{}{0:C2}" />
Right now, "Price" will default to 0. The UI will initially show $0.00 because of the StringFormat. That is working fine. When I put focus into the control, I only see 0, that is also fine. The issue is when I try to type a decimal. The value disappears and I see an issue in my Output that says -- Binding: can not be converted to type 'System.Int32'
Example steps:
**** Also, the Version of the Telerik controls I am using is -- 2019.2.603.360. The drop down below doesn't let me choose that version.
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
When using Xamarin.Forms 3.6 and UI for Xamarin 2019.1.316, the RadNumericInput control does not fire the Unfocused event (on Android and iOS).
This can be easily reproduced using the following code:
<telerikInput:RadNumericInput x:Name="BuyerAmount" Unfocused="BuyerAmount_OnUnfocused" StringFormat="{}{0:C2}"/>
As a temporary workaround, I am able to get the Unfocused event from the ControlTemplate's internal NumericInputEntry control:
<numericInput:NumericInputEntry x:Name="PART_Entry" Unfocused="BuyerAmount_OnUnfocused" ... />
This is a very unattractive solution as I need to define a separate ControlTemplate for every control instance that I need separate event handlers.
Value is not applied correctly when StringFormat property is used (N format specifier): For example
<telerikInput:RadNumericInput StringFormat="{}{0:N0}"
Value="{1234.56543}"/>
Hello,
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.
Current behavior
the NumericInput color is using the accent color for all states. We can't guess whether the control is focused or not.
Expected behavior
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.
Workaround
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.
Best regards
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
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.
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.