BoucherS_cp
015d89f201
9 years ago
BoucherS_cp
fcc59e8737
Version 2.9
10 years ago
BoucherS_cp
854027e890
11 years ago
BoucherS_cp
af8b733790
11 years ago
BoucherS_cp
964cdfeb69
12 years ago
BoucherS_cp
ac5ca4f242
12 years ago
BoucherS_cp
8598422abe
12 years ago
BoucherS_cp
925cbcd472
12 years ago
emartin_cp
983f425e67
Version 2.0
13 years ago
emartin_cp
0d9a63a7d2
Version 1.9
13 years ago
emartin_cp
a64bb838eb
Rename WPFToolkit.Extended directories for Xceed.Wpf.Toolkit
13 years ago
emartin_cp
f068898687
1.8.0 Release - Various deployment fixes
14 years ago
emartin_cp
0c933c8124
1.8.0 Release
14 years ago
emartin_cp
2edfd42354
1.7.0 Release
14 years ago
Nebuleux_cp
1f0dbeb7e0
Change the license back to Microsoft Public (Ms-PL) in the header of every .cs and .xaml files.
14 years ago
Nebuleux_cp
a5a5359315
Change the namespaces.
14 years ago
Nebuleux_cp
f0775d4061
Add a license description in the header of every .cs and .xaml files.
14 years ago
brianlagunas_cp
ecb8324c33
fixed all OnApplyTemplate overrides that hook into events.
14 years ago
brianlagunas_cp
19ea540264
InputBase and UpDownBase controls: BREAKING CHANGE - renamed IsEditable to IsReadOnly and implemented accordingly.
15 years ago
brianlagunas_cp
305b4551f4
UpDown controls: added MouseWheelActiveOnFocus property which allows you to decide if the control must have focus in order for the mouse wheel to incement/decrement the value. True by default.
15 years ago
brianlagunas_cp
256bc70a27
Numeric UpDown editors: fixed issue with with Value being set before the newValue is coerced and then having the Value set again. Now the Value is coerced and set only once.
15 years ago
brianlagunas_cp
9d90261826
UpDown editors: due to a bug in Visual Studio, you cannot create event handlers for events that have generic or nullable event args in XAML. So I changed the event args to object to support the design experience, but this now forces you to cast the result of the new value to the appropriate data type.
Various bug fixes
15 years ago
brianlagunas_cp
a2ba2885ec
UpDownBase: found issue in .NET 3.5 version with updating text.
15 years ago
brianlagunas_cp
8448087086
Getting ready for v1.4 release
15 years ago
brianlagunas_cp
9858a1e81f
numeric editors: minor changes.
15 years ago
brianlagunas_cp
b7b88c6903
removed NumericUpDown control.
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
6f5d844125
checked in initial IntegerUpDown control. Not ready for use, just getting it in the code base.
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
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
70f5b84375
ButtonSpinner: Added AllowSpin and ShowButtonSpinner properties
UpDownBase: Added AllowSpin and ShowButtonSpinner properties
15 years ago
brianlagunas_cp
c028c06421
Moved UpDownBase into the primitives namespace.
15 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
e04f959612
fixed some stuff I broke, and improved data type conversions
16 years ago
brianlagunas_cp
34e7fd56df
Made a lot of changes, and possible breaking changes:
1. added new MaskedTextBox control
2. no longer have UpDownBase<T>
3. NumericUpDown now has new base class. Hopefully I didn't break anything, but I know I did :0)
4. By default the NumericUpDown uses doubles. To use anything else such as decimals or int you must specify the ValueType accordingly.
<extToolkit:NumericUpDown Grid.Row="1" Value="{Binding Age}" Increment="1" Minimum="18" Maximum="65" ValueType="{x:Type sys:Int32}" />
16 years ago