11 Commits (b3b7d9d452bb20269ec2043979ddca2fb148a06b)

Author SHA1 Message Date
brianlagunas_cp cd5b6355a9 DateTimeUpDown: fixed bug with CultureInfo 15 years ago
brianlagunas_cp 19ea540264 InputBase and UpDownBase controls: BREAKING CHANGE - renamed IsEditable to IsReadOnly and implemented accordingly. 15 years ago
brianlagunas_cp 816de91c66 NUmeric UpDown editors: Fixed .NET 3.5 bug with TextAlignment property. 15 years ago
brianlagunas_cp 51e6a10b9f check in of new DecimalUpDown and DoubleUpDown. All numeric UpDown controls shoudl be functional. Now it is time to refactor. 15 years ago
brianlagunas_cp 9d85504a12 In order to reliably support the different numeric data types, I need to create a specific control for each data type. So instead of copying and pasting I am going to try to create a generic base class that has most of the logic in it. This will make the NumericUpDown control obsolete and it will be removed from the toolkit. The new controls will be DecimalUpDown, DoubleUpDown, and IntegerUpDown. 15 years ago
brianlagunas_cp af6d43a151 Added Watermark and WatermarkTemplate to all controls derived from InputBase. 15 years ago
brianlagunas_cp faa7825423 Major overhaul of NumericUpDown, DateTimeUpDown, and MaskedTextBox in order to support null values. Need extensive testing because I am sure I broke something. 15 years ago
brianlagunas_cp 37ca2046a3 Added ValueChanged event to DateTimeUpDown and NumericUpDown. 16 years ago
brianlagunas_cp 05b6f8024d InputBase: Renamed DisplayText back to Text. made more sense and I didn't want to go change all the documentation to DisplayText :0P 16 years ago
brianlagunas_cp 403c43dc31 NumericUpDown: constrained the Value between the Min and Max values. 16 years ago
brianlagunas_cp 34e7fd56df Made a lot of changes, and possible breaking changes: 16 years ago