SfNumericUpDown range constraints prevent control operation

[Tim Coulter]

Hello,

I have a Xamarin.Forms Android app in which I am attempting to install the Syncfusion SfNumericUpDown control.

If I configure the control without explicit Minimum and Maximum constraints, its editing functionality works correctly.

Equally, if I apply range constraints via a Style, it also works correctly and the constraints are respected.

However, if I apply Minimum or Maximum values directly to the control, it prevents the spinner buttons from changing the control value (even when the control value is within the permitted range).

Is this a bug in the control or something that I am doing wrong?

Thanks,

Tim

[Hemalatha Marikumar]

Hi Tim,

Thanks for contacting Syncfusion Support.

We were unable to reproduce the reported issue at our end. We have attached a sample to test the issue for your reference in the below location.

Link: http://www.syncfusion.com/downloads/support/forum/124792/ze/NumericUpDown-1068075287  

Please check the sample and if the issue still persists, update us the modified sample or the replication procedure to analyze further and provide the solution for the problem.

Regards,
Hemalatha M.R

[Tobias Högefjord]

I also have this problem. It is when Minimum is over 1, 0 and 1 is OK. But anything else is blocking spinner buttons. I have tested in the big sample project.

BR

Tobias

[Pavendhan Kumar]

Hi Tobias

We were able to reproduce the mentioned issue "When NumericUpDown's minimum is set to other than 0 or 1 blocks the spinner button’s operation" at our end. And we have logged the bug report for the same. A support incident to track the status of this issue has been created under your account. Please log on to our support website to check for further updates

https://www.syncfusion.com/account/login?ReturnUrl=%2fsupport%2fdirecttrac%2fincidents 

Regards,
Pavendhan K.