Home Dashboard Directory Help

NumericUpDown Value Change by jarrred


 as Won't Fix Help for as Won't Fix

Sign in
to vote
Type: Bug
ID: 238370
Opened: 11/15/2006 6:06:57 PM
Access Restriction: Public
User(s) can reproduce this bug


When changing NumericUpDown after delete keys has been pushed while value was highlight left to right or highlighted from code using select method and these sequence of events have occured twice or more when the value is updated the control will not display the new value.
Sign in to post a comment.
Posted by jarrred on 4/2/2007 at 5:49 PM
Would love to have hotfix for system.windows.forms
Posted by Microsoft on 1/31/2007 at 5:01 PM
Thanks for your feedback on the .NET Framework! As you may have seen in DevDiv VP - S. Somasegar’s blog on the topic (http://blogs.msdn.com/somasegar/archive/2006/05/18/601354.aspx) the next release of the .NET Framework (codenamed “Orcas”) requires a high degree of backwards compatibility. As such we are not able to address this issue with a fix in the .NET Framework in the Orcas timeframe. Many customers have found it useful to discuss issues like this in the forums (http://forums.microsoft.com/msdn/default.aspx?siteid=1) where Microsoft and other members of the community can suggest workarounds.

Before we even begin work on the next release of the NET Framework release where we can make changes like this one we will devote time to addressing the top issues (in terms of number of votes, lack of workarounds, etc). So please do continue to vote for this item if it is causing issues.

Thanks and keep the feedback coming.

UIFx Team
Posted by jarrred on 11/15/2006 at 6:10 PM
Please see my project as there are many steps.
> add numeric updown
> add button to set value of textbox
> run project
> highlight numeric value by double clicking numeric textbox
> press delete key
> set new value by using command button
> highlight numeric value by double clicking numeric textbox
> press delete key
> now press button to set new value
Sign in to post a workaround.
Posted by jarrred on 11/20/2006 at 2:34 PM
I know this is going to reduce my chance of having bug fixed, however I figured NetFX 3.5 is at least 1-2 years away and this is another little bug with workaround.

Workaround 1: change value of control

numericbox.value += 1
numericbox.value -= 1

Workaround 2: if del key is intended for the form and not control then you could get around it with following code

e.supresskey = true