56f8bf9170
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.
16 years ago
0ab8930ac5
NUmeric UpDown editors: Fixed .NET 3.5 bug with TextAlignment property.
16 years ago
ed30b7367b
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
9e0ece8f58
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
16 years ago
381292c8a2
UpDownBase: found issue in .NET 3.5 version with updating text.
16 years ago
6d08df0493
Getting ready for v1.4 release
16 years ago
e05d6b9d09
Calculator: missed a localization spot
16 years ago
c1ebeba092
Calculator: localize value
16 years ago
e2a3ea153a
numeric editors: minor changes.
16 years ago
bc3eb7e104
removed NumericUpDown control.
16 years ago
b2a10a7929
check in of new DecimalUpDown and DoubleUpDown. All numeric UpDown controls shoudl be functional. Now it is time to refactor.
16 years ago
4a64011c1b
checked in initial IntegerUpDown control. Not ready for use, just getting it in the code base.
16 years ago
a39e55b365
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.
16 years ago
89fcc42bd2
Added Watermark and WatermarkTemplate to all controls derived from InputBase.
16 years ago
8ed67339d5
Major overhaul of NumericUpDown, DateTimeUpDown, and MaskedTextBox in order to support null values. Need extensive testing because I am sure I broke something.
16 years ago
75d382e2d4
Calculator: implemented memory functions
16 years ago
ba7bd4bcd6
Calculator: got the rest of math functions working. Now I am moving on to the Memory functions.
16 years ago
4d088d105f
Calculator: got basic math working.
16 years ago
a24b67f38c
Working on Calculator
16 years ago
6a390c4aff
ButtonSpinner: Added AllowSpin and ShowButtonSpinner properties
UpDownBase: Added AllowSpin and ShowButtonSpinner properties
16 years ago
895d6d0156
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.
16 years ago
109f58569e
check-in initial TimePicker control. Not ready to be used, still trying to decide what approach to take to develop it.
16 years ago
c906b95336
ColorPicker: implemented ColorCanvas control. ColorPicker now has an advanced color palette to choose colors form.
16 years ago
f0906048a4
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.
16 years ago
e9aedfdcf7
PropertyGrid: Working on property options, and ValueSource icons.
16 years ago
ebdaa9936e
ColorToSolidColorBrushConverter: implemented ConvertBack method. Although not used in the toolkit, a user has requested this functionaltiy and provided a patch.
16 years ago
91212cae5e
Moved UpDownBase into the primitives namespace.
16 years ago
7f0119cf3b
ColorPicker: added transparent color swatch to Standard Colors. Fixed minor binding errors.
16 years ago
a55ce6ee12
Added ValueChanged event to DateTimeUpDown and NumericUpDown.
16 years ago
0903d0b59c
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
b8d85b1646
NumericUpDown: constrained the Value between the Min and Max values.
16 years ago
df80d9ff11
fixed some stuff I broke, and improved data type conversions
16 years ago
5f3d93c5f6
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
01e62e0cd4
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
af0bfa7ada
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
04bac5a0a7
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
brianlagunas_cp