At 10:37 PM 10/06/2005 +1000, JBA wrote: >Hey guys, > >I saw a commit that said NumericUpDown was implemented so I wired it >into MonthCalendar (which should now be considered feature complete). > >Along the way I discovered what I think are bugs in NumericUpDown. If >NumericUpDown is not actually complete yet then feel free to ignore >these points:
Well, it should essentially be complete, but let's see what you've got. >- Setting the Value property for the numeric up down control while it's >not visible results in that value not being set. I believe the flow is >this: > Set .Visible = false > Set .Minimum > .Value now has .Minimum as it's value > Set .Value; > .Value calls one of the updateedit method which inturn uses a parseedit >method which for some reason reads the minimum value as the current text >and so .Value gets reset to parsed minimum value. I wrote up a test case but was unable to reproduce your results. Can you reduce it to a minimal test case for me? >- It's not responding to Readonly property correctly (.ReadOnly = true >means up/down buttons work but not text editing. This is the correct behaviour for .ReadOnly. >- It seems to render buttons on windows for me, but not on linux This is probably a bug in mono's ControlPaint or whatever ControlPaint calls (something in the theme library). >- It doesn't seem to be handling the key press events (this may be an >issue with the way I'm using it though). It does for me :-) >There was something else about the way MonthCalendar render's on linux >but I can't remember it now. Will send that through when I remember. Okay :-) Jonathan Gilbert _______________________________________________ Mono-winforms-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-winforms-list
