Unplanned
Last Updated: 09 Nov 2022 12:42 by ADMIN
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.
Completed
Last Updated: 14 Sep 2022 13:54 by ADMIN
Release R3 2022
When changing the device culture to culture that requires comma as decimal separator (for example, German) - pressing the comma key does not work. You must press period. When pressing period "." -> "," is entered.
Completed
Last Updated: 19 Jan 2022 13:58 by ADMIN
Release R1 2022
On Samsung phones, the decimal separator and minus sign are in the same keyboard button and you press it once for the decimal sign to be written and press it twice for the minus sign to be written. After some tests, I found that this works fine on cultures that use "." as the decimal separator, but not on cultures that use "," (like Portuguese).

 

What happens is that no matter how many times you press the ", / -" button, it never writes the minus sign, therefore doesn't allow writing negative numbers.
Unplanned
Last Updated: 28 Feb 2020 09:19 by ADMIN
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. 
Unplanned
Last Updated: 11 Dec 2019 11:32 by ADMIN
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
Completed
Last Updated: 24 Jun 2020 12:05 by ADMIN
Release R2 2020 SP
If there are input controls inside the templates, updating a property of any data item though an input control ( such as Entry, NumericInput, etc),  caused the control to lose focus.
Completed
Last Updated: 31 Jan 2024 09:17 by ADMIN
Release R1 2021 SP1
Created by: Travis
Comments: 7
Category: NumericInput
Type: Bug Report
3

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:

  • With the value set to 0.00
  • Focus the control -- you will now see just 0
  • Press the decimal key (aka the period key)
  • Notice the error in the Output window in VS and also the control shows nothing at all
  • If you press the decimal key again, you will see two decimals in the control

**** 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.

Unplanned
Last Updated: 01 Jul 2019 08:16 by ADMIN
Created by: AscanioTziazas
Comments: 1
Category: NumericInput
Type: Feature Request
3

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

Completed
Last Updated: 23 Oct 2019 12:25 by ADMIN
Release R3 2019 SP
Created by: Jason
Comments: 1
Category: NumericInput
Type: Bug Report
1

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).

Reproduce

This can be easily reproduced using the following code:

<telerikInput:RadNumericInput x:Name="BuyerAmount" Unfocused="BuyerAmount_OnUnfocused" StringFormat="{}{0:C2}"/>

Workaround

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.

Completed
Last Updated: 03 Jun 2019 14:41 by ADMIN
Release 2019.2.603.360 (R2 2019 minor release)

Value is not applied correctly when StringFormat property is used (N format specifier): For example

 <telerikInput:RadNumericInput StringFormat="{}{0:N0}"
                                               Value="{1234.56543}"/>

 Workaround:

use F format specifier instead of N format specifier
Completed
Last Updated: 13 May 2020 13:15 by ADMIN
Release R2 2020
The default value of NumericInput is 0, so when Minimum higher than 0 is set, the increase and decrease buttons are disabled.  The erroneous behavior can be observed when the Telerik theme is applied, or when the ControlTemplate is modified.
Unplanned
Last Updated: 18 Apr 2019 14:51 by ADMIN
Having a property in the control that could toggle decimal to whole numbers would be a good improvement to the control.
Declined
Last Updated: 19 Feb 2019 08:31 by ADMIN
Created by: Olivier
Comments: 2
Category: NumericInput
Type: Bug Report
0

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

Unplanned
Last Updated: 19 Feb 2019 08:05 by ADMIN
Created by: Olivier
Comments: 1
Category: NumericInput
Type: Feature Request
2

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

Unplanned
Last Updated: 26 Sep 2018 12:23 by Vardan
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 
Unplanned
Last Updated: 05 Sep 2022 13:17 by ADMIN
Created by: Vardan
Comments: 5
Category: NumericInput
Type: Bug Report
2
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  
Completed
Last Updated: 21 Aug 2018 11:37 by ADMIN
Created by: Gagik
Comments: 1
Category: NumericInput
Type: Bug Report
0
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.
Unplanned
Last Updated: 17 Jul 2018 14:21 by ADMIN
Created by: Gagik
Comments: 1
Category: NumericInput
Type: Bug Report
0
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.
Completed
Last Updated: 22 Nov 2018 16:15 by ADMIN
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.
Completed
Last Updated: 21 Jun 2018 13:06 by ADMIN
Available in the R2 2018 release.
1 2