[Mono-bugs] [Bug 79001][Min] Changed - [Patch]: NumericUpDown: Value proeprty should be equal to Minimum property when created

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Aug 3 16:42:21 EDT 2006

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by alex.olk at googlemail.com.


--- shadow/79001	2006-08-03 15:59:21.000000000 -0400
+++ shadow/79001.tmp.31733	2006-08-03 16:42:21.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 79001
 Product: Mono: Class Libraries
 Version: 1.1
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Minor
 Component: Windows.Forms
 AssignedTo: peter at novonyx.com                            
 ReportedBy: unserkonig at gmail.com               
 QAContact: mono-bugs at ximian.com
@@ -69,6 +69,24 @@
 this, but do we properly reset the textbox value to be within min/max 
 if the user manually enters a number?
 ------- Additional Comments From unserkonig at gmail.com  2006-08-03 15:59 -------
 Currently, if the user manually enters a value that isn't within
 min/max, the value is not changed to be in the range (.Net does).
+------- Additional Comments From alex.olk at googlemail.com  2006-08-03 16:42 -------
+Fixed in revision 63325.
+And for Peter:
+Manually user number entry is ok. The only problem is that the caret
+stays (if it is even visible) at the same position instead of moving
+with the entered char to the next position.
+Moving the cursor with the cursor keys doesn't work either (selecting
+the cursor pos with the mouse is a no go too).
+The same applies to the textbox in ComboBox.

More information about the mono-bugs mailing list