NumericUpDown IsEditable property does not work well

[Rogério]

Hello,

I'm using RadNumericUpDown and in some occasions I'd like to set it like "ReadOnly"! The approximated property that I found is IsEditable!

When setting IsEditable to false, the controls allows to delete content with keyboard and also to change value using mouse clicks on arrows.

Is there any work-arround for this issue? Do you have any plans to fix it?

Thanks.

Best Regards,
Rogério

[John]

I just ran into this problem myself and the solution is to set the INCREMENT to 0.  Then nothing happens when the arrows are pressed.

[Valeri Hristov]

Hi Rogério,

We will address the issues around the IsEditable property with one of the next updates of RadControls for Silverlight. As a workaround I would suggest when you don't want to let your users to edit the control value to set its IsEnabled property to false.

Sincerely yours,
Valeri Hristov
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Walter]

Hello Valeri Hristov,

it seems that IsEditable is still not working in Q3/2009.
Could you please confirm and inform me when the problem will be fixed.

Kind regards
Daniel

[Valeri Hristov]

Hi Daniel,

It seems that we introduced this bug again while fixing another. I apologize for the inconvenience, today an internal build will be published, that will contain the fix of this problem.

Regards,
Valeri Hristov
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Justin Lee]

I'm using Q1 2011, and IsEditable still doesn't appear to work.  I have a NumericUpDown and set IsEnabled to false, but I am still able to change the value.  Any update on this?

Thanks,
Justin

[Justin Lee]

I should have specified...  With IsEnabled = false, I cannot change the value by typing a number, but I can change it by using the arrow keys or by clicking on the Up/Down buttons.  Is this as designed?  If so, is IsEnabled the only option?  (I'd rather not use IsEnabled because its so hard to read when disabled)

[Valeri Hristov]

I am afraid that the IsEditable prevents the TextBox in RadNumericUpDown from receiving text input (we set IsReadOnly=true), but the buttons are allowed to be clicked. You could try also setting ShowButtons=false when you have IsEditable=false - this way the buttons will not be visible and the TextBox will not be editable.

Greetings,
Valeri Hristov
the Telerik team

[Justin Lee]

IsEditable = false and ShowButtons = false would ALMOST work... The only issue with that the user can still change the value by using the UP and DOWN keys.

Looks like I'll have to use IsEnabled, or replace it with a Readonly textbox when I don't want the user to edit it.

Thanks,
Justin

[BigShoes]

Justin,

Simply set the LargeCharge and the SmallChange properties to 0 when you want to disable the ability of the user to press up/down keys when IsEditable = False. 

[Matt]

Is there ever going to be a fix for this? It seems like it would be an easy fix to ignore the UP and DOWN keys if the control is set to IsEditable=false.

[Konstantina]

Hi Matt,

This is the behavior of the NumericUpDown control by design - since you are able to change the value with the buttons, it is normal to be able to change the value with the Up and Down keys. You could handle the KeyDown event and cancel it when the control has set IsEditable=False.

Regards,
Konstantina
Telerik

 

 

[Matt]

Yes, when IsEditable==False, you are able to change the value with the buttons. I would argue that this behavior is also wrong. (Are you not editing the value?)

If this is by design, then I would argue that the control should have an IsReadOnly property that would prevent any value changes. (Using IsEnabled==False is not an acceptable solution. A disabled control cannot receive focus, its value cannot be selected and copied, and it cannot trigger mouse events - to initiate context menus, for example.)

Your suggested solution of handling the KeyDown event and cancelling the event does not work. Unfortunately, the way the RadNumericUpDown control itself handles the KeyDown event prevents the user from cancelling the event.

[Konstantina]

Hello,

I have logged the ReadOnly feature request. You could vote for it in our feedback portal: http://feedback.telerik.com/Project/143/Feedback/Details/123258-add-readonly-property-to-the-numericupdown-control
Please, if you have any notes, feel free to add them there.
If it receives enough clients' requests we will put it in our development plan.

Regards,
Konstantina
Telerik

 

 

[Jonathan]

You have got to be kidding me.

Anyone with a bit of common sense can see this is an obvious bug.

Every suggestion in this post is an unacceptable workaround, and to blame the buttons and say this is by design is simply a joke.

If you have a property called IsEditable on a control, it can only mean one thing; Either the control is editable or it is not, there are no middle cases here.

We are in the middle of 2015, 6 years after you initially (correctly) confirmed this to be a bug.

These kind of situations are what makes potential customers stay on the fence..

Please take notice..  Jonathan.

[Georgi]

Hi Jonathan,

Thank you for the feedback.

We also agree that introducing the ReadOnly property needs to be addressed. Also, please note that as the Q2 2015 is just around the corner we will be planning the items for the next release and we will definitely consider the feature. Also you can subscribe for the feedback item so you will be notified when its status is changed.

Nevertheless we are sorry for the inconvenience caused.

Regards,
Georgi
Telerik

[Jonathan]

Hi Georgi,

Ignoring everything I said means we disagree.

As I said, this is not a feature request, this is clearly a bug involving IsEditable property.

You are suggesting to ignore the bug, and consider a new feature. If there is an IsEditable property, why would you need a ReadOnly property as well?  How would you explain the difference in them?

Would you write in the documentation that IsEditable makes the control semi-readonly? 

You do realize that currently the documentation is completely wrong: "Gets or sets the value indicating whether the control is editable or not". - It is editable. always.

[Georgi]

Hello Jonathan,

As editing given input control (RadComboBox for example) is usually associated with typing, deleting and retyping in the control setting IsEditable = False for the RadNumericUpDown stops the editing - cannot input in the TextBox part of the control.
Therefore as there is a user demand for functionality that will prevent the change of the value via the UI of the control we have decided to add the IsReadOnly property.

Also you can use the Silverlight Tookit NumericUpDown for reference as in there the IsEditable property also prevents the users to change the value via its TextBox part.

Nevertheless the documentation indeed does not provide clear information on the property behavior and will do our best to improve it in the future.

Regards,
Georgi
Telerik

[Shyam]

Hi,

I just want to disable the RadNumericUpDown (Up and down arrows should not change the value). I tried using IsEnabled, IsEditable, and IsReadOnly. Now IsReadOnly is not available and IsEnabled and IsEditable does not work with arrow keys. How can I bind them then?

[Kalin]

Hi,

I already replied you in the support ticket regarding the same question. I'm coping my reply here in order to be available to the community:

The NumericUpDown control now provides IsReadOnly property (it was introduced with Q2 2015 SP1) - it disables the buttons and input field. For more details please check the following article from our online help documentation:
http://docs.telerik.com/devtools/wpf/controls/radnumericupdown/features/behavior

You can test it in our Silverlight demos on the link below:
http://demos.telerik.com/silverlight/#NumericUpDown/Configurator

If this is the desired behavior I would recommend upgrading to the latest release version of UI for WPF. If you need something else, I would like to ask you to share some more details regarding the exact behavior you need to support.

Hope this helps.

Regards,
Kalin
Telerik