brianlagunas_cp
|
e129c60465
|
DateTimeParser: now correctly parses SortableDateTime and UniversalSortableDateTime formats
|
15 years ago |
brianlagunas_cp
|
8931793f6b
|
forgot to remove test code.
|
15 years ago |
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
|
d8f5f1f0f1
|
DateTimeUpDown/DateTimePicker: fixed applying a custom format when the FormatString is defined first in XAML.
|
15 years ago |
brianlagunas_cp
|
59c178e4cc
|
DateTimeParser: added support for cultures that have "." as a date/time separator such as Danish.
|
15 years ago |
brianlagunas_cp
|
5e687f11ef
|
DateTimeParser: fixed exception when Format is null
|
15 years ago |
brianlagunas_cp
|
8e22d5cf2c
|
DateTimePicker: fixed issue with custom format and binding the same dateTime to multiple DateTime controls.
|
15 years ago |
brianlagunas_cp
|
4beca7ad28
|
DateTime controls: improved the date time parsing to better support different cultures.
|
15 years ago |
brianlagunas_cp
|
c39ed7c020
|
TimePicker: fixed bug when trying to use a Custom format and FormatString. Reved to 1.4.0.2.
|
15 years ago |
brianlagunas_cp
|
43564c3cce
|
DateTimeUpDown: fixed bug when using custom formats and IsEditable = true
|
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
|
c3b25b60ad
|
DateTimePicker and TimePicker: added Watermark and WatermarkTemplate properties. Also fixed small bug in the DateTimePicker.
|
15 years ago |
brianlagunas_cp
|
b7b88c6903
|
removed NumericUpDown control.
|
15 years ago |
brianlagunas_cp
|
ccdae8bb19
|
NumericUpDown and DateTimeUpDown: Renamed NullValue to DefaultValue.
|
15 years ago |
brianlagunas_cp
|
55c9ce7f55
|
small misc fixed and changes.
|
15 years ago |
brianlagunas_cp
|
6a0c61dbae
|
DateTimeUpDown: got date/time editing working for most common patterns. If the DateTime value has characters between the different DateTime parts such as T or Z, it will not work correctly.
Example: 2011-03-30T10:00:07 and 2011-03-30 10:01:21Z will not be editable.
|
15 years ago |
brianlagunas_cp
|
35c134a302
|
DateTimeUpDown: fixed bug I just introduced.
|
15 years ago |
brianlagunas_cp
|
c4b66dce21
|
DateTimeUpDown: working on making the control editable (enter values with keyboard). Only have the date editing working. Still working on the time editing.
|
15 years ago |
brianlagunas_cp
|
0669e78ec7
|
NumericUpDown and DateTimeUpDown: added NullValue property which allows you to set a default value if the bound value is null. The NullValue will be used when the increment/decrement buttons are pressed on a null value.
|
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
|
8d02413ea0
|
DateTimeUpDown: fixed bug when DateTimePart selection would not be correct when setting the Value property first in XAML.
|
15 years ago |
brianlagunas_cp
|
d48a3d1211
|
Major overhaul of folder structure. Seperated Generic resource dictionary into smaller more managable resource dictionaries (one for each control). This will also help add support for theming. Hopefully I didn't break anything.
|
15 years ago |