tsai
/
wpftoolkit
mirror of https://github.com/xceedsoftware/wpftoolkit.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
403 Commits
4 Branches
18 Tags
62 MiB
Tree: 751d606bda
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '751d606bda'
${ noResults }
Commit Graph

10 Commits (751d606bdaa109f20093797805c30f52e513eed2)

Author SHA1 Message Date
emartin_cp 0c933c8124 1.8.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.
15 years ago
Nebuleux_cp a5a5359315 Change the namespaces.
15 years ago
Nebuleux_cp f0775d4061 Add a license description in the header of every .cs and .xaml files.
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.
16 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.
16 years ago
brianlagunas_cp bbb53816ce numeric updown controls: fixed the percent formatting
16 years ago
brianlagunas_cp 8e5c79604a refactored new numeric editors and added the editors to the PropertyGrid control. Now time to start ripping out the old NumericUpDown control.
16 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.
16 years ago
brianlagunas_cp 6f5d844125 checked in initial IntegerUpDown control. Not ready for use, just getting it in the code base.
16 years ago