I'm using Infragistics XAM numeric input in my view and i've specified the Min Inclusive and Max Exclusive values.I'm allowing the user type the values in the control apart from giving the spinner button.
Max inclusive works fine and it does not allow the user to type a value greater than Max Exclusive.
But
Min Inclusive allows the user to type a value below the Min Inclusive.
eg: If Min Inclusive is 1 it allows the User to enter 0.
But if Max Inclusive is 365 the user is restricted from entering the value greater than 365.
This should be the behavior for the Min Value as well
P.S :Spinner buttons work properly for the Min and Max ranges.
Hello Adidev,
I am just checking the progress of this issue and was wondering if you managed to achieve your goal or if you need any further assistance on the matter.
You can use XamNumericEditor instead, where you can choose what to be the invalid value behavior, by setting the InvalidValueNehavior Property. Here you can find more information:
http://help.infragistics.com/Help/Doc/WPF/2012.1/CLR4.0/html/InfragisticsWPF4.Editors.v12.1~Infragistics.Windows.Editors.ValueEditor~InvalidValueBehavior.html
Please let me know if you have further questions on this matter.
Hello Stefan,
I'm facing the same problem as well.
The Logic you specified holds good if the Min Inclusive is 2 but when you set the MinInclusive to 1 and for our requirement we want the user to specify time duration and allowing him to enter a 0 would be incorrect,also from our application we are not allowed to have pop ups,so now if you could help me how i can handle this where in
I should not allow the user to enter 0 and also i should avoid the pop up that says that the value entered should be greater than Min Inclusive.
To be precise i'd want the same behavior of XAMnumeric input that is there for MaxInclsuive for MinInclusive as well .How can i achieve it.
Hello Abishek,
Thank you for your post. I have been looking into and I can say that this behavior is by design, because if you have MinInclusive set to 2 you should be able to enter 1, because we cannot determine whether you will continue to enter numbers and enter 10 for example or you will stop. This is the logic used for all the MinInclusive values. Please let me know if this helps you or you have further questions on this matter.
Looking forward for your reply.