brianlagunas_cp
816de91c66
NUmeric UpDown editors: Fixed .NET 3.5 bug with TextAlignment property.
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
7fe3ee4d96
Calculator: missed a localization spot
15 years ago
brianlagunas_cp
504f833b7e
Calculator: localize value
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
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
a78bf7baae
Calculator: implemented memory functions
15 years ago
brianlagunas_cp
87f7305430
Calculator: got the rest of math functions working. Now I am moving on to the Memory functions.
15 years ago
brianlagunas_cp
67b8175d62
Calculator: got basic math working.
15 years ago
brianlagunas_cp
7d6b612fff
Working on Calculator
15 years ago
brianlagunas_cp
70f5b84375
ButtonSpinner: Added AllowSpin and ShowButtonSpinner properties
UpDownBase: Added AllowSpin and ShowButtonSpinner properties
15 years ago
brianlagunas_cp
2f50c837b6
Merged all current 4.0 changes into the 3.5 solution. Didn't fully test all controls, but they all compile and seem to work. Not sure how much longer I will support 3.5 since it is so time consuming and a pain to do it.
15 years ago
brianlagunas_cp
f3091ccbc5
check-in initial TimePicker control. Not ready to be used, still trying to decide what approach to take to develop it.
15 years ago
brianlagunas_cp
833623716a
ColorPicker: implemented ColorCanvas control. ColorPicker now has an advanced color palette to choose colors form.
15 years ago
brianlagunas_cp
a030fcd934
initial checkin of new ColorCanvas control. This is an advanced color control that is not within a popup, but acts as a stand alone control that allows you to select colors by using a color canvas, or by setting RGB and Alpha values.
15 years ago
brianlagunas_cp
85bfc4484f
PropertyGrid: Working on property options, and ValueSource icons.
15 years ago
brianlagunas_cp
c77febf480
ColorToSolidColorBrushConverter: implemented ConvertBack method. Although not used in the toolkit, a user has requested this functionaltiy and provided a patch.
15 years ago
brianlagunas_cp
c028c06421
Moved UpDownBase into the primitives namespace.
15 years ago
brianlagunas_cp
99f34fec54
ColorPicker: added transparent color swatch to Standard Colors. Fixed minor binding errors.
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
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
brianlagunas_cp
532dab48f0
added new NumericUpDown control. It provides spin buttons to increment and decrement the value. You can also specifiy a format in which to show the value such as currency C2, or decimal up to three decimals F3. YOu can specify a Min and Max value as well as the increment values. You can also specify if the user can type in the textbox by setting IsEditable property. Support for up/down arrows and mouse wheel.
<toolkit:NumericUpDown Value="25" FormatString="C2" Increment=".5" Maximum="30" Minimum="20" />
16 years ago
brianlagunas_cp
308ad9dc85
initial checkin of new ButtonSpinner control. Allows you to add button spinners to any element and then respond to the Spin event to manipulate that element. To add use the following syntax
<toolkit:ButtonSpinner Spin="ButtonSpinner_Spin" >
<TextBox x:Name="_txtValue" />
</toolkit:ButtonSpinner>
private void ButtonSpinner_Spin(object sender, Microsoft.Windows.Controls.Primitives.SpinEventArgs e)
{
int value = String.IsNullOrEmpty(_txtValue.Text) ? 0 : Convert.ToInt32(_txtValue.Text);
if (e.Direction == Microsoft.Windows.Controls.Primitives.SpinDirection.Increase)
value++;
else
value--;
_txtValue.Text = value.ToString();
}
16 years ago
brianlagunas_cp
140533ed75
RichTextBox: Removed the AllowFormatting property and completely changed the way the format bar works. The format bar is now a seperate control and can be used either on the deafult RichTextBox or the toolkit's RichTextBox. The format bar is used in conjunction with a format bar manager class. You add the format bar as follows
<toolkit:RichTextBox>
<toolkit:RichTextBoxFormatBarManager.FormatBar>
<toolkit:RichTextBoxFormatBar />
</toolkit:RichTextBoxFormatBarManager.FormatBar>
</toolkit:RichTextBox>
or on the default RichTextBox like so
<RichTextBox >
<toolkit:RichTextBoxFormatBarManager.FormatBar>
<toolkit:RichTextBoxFormatBar />
</toolkit:RichTextBoxFormatBarManager.FormatBar>
</RichTextBox>
You can also create your own format bar by inheriting from IRichTextBoxFormatBar.
16 years ago