Quantcast
Channel: Extended WPF Toolkit™ Community Edition
Viewing all 4964 articles
Browse latest View live

New Post: DoubleUpDown.IsEditable gone?

$
0
0
Ah, my bad- I was using version 1.5. Would it be possible for you guys to add in the functionality that was originally present with the IsEditable property in 1.5? IsReadOnly disables the entire control, not just the arrows.

New Post: DoubleUpDown.IsEditable gone?

$
0
0
The "AllowSpin" property allow you to control if the user can "spin" the values, with the "spin buttons", the keyboard arrows or mouse wheel.
The "ShowButtonSpinner" allow you to show or hide the "spin buttons".
The "MouseWheelActiveTrigger" property allow you to control if and when the mouse wheel can "spin" the buttons. (only when AllowSpin is true. Of course)

New Post: DoubleUpDown.IsEditable gone?

$
0
0
Sorry, I did not make myself clear. I would like to cause the DoubleUpDown to NOT be editable by entering a number in the field using the keyboard, but the arrows to still work.

Created Unassigned: DoubleUpDown.IsEditable gone? [19754]

$
0
0
From discussion:
https://wpftoolkit.codeplex.com/discussions/444607

IsReadOnly property has replaced "IsEditable" since v1.6.
But the current property (IsReadOnly) disable all input.
The legacy behavior was to only disable text input, keeping the button spinner working.
(To confirm the legacy behavior with the keyboard arrows and mouse wheel)

We should have the option to prevent text input without preventing the user to spin.

Probably something like a "AllowTextInput" property.

New Post: DoubleUpDown.IsEditable gone?

$
0
0
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.

New Post: DoubleUpDown.IsEditable gone?

New Post: DataGrid: Change the "Drag a column ..." text

$
0
0
Hello MyKey0815,

try this:
<Style TargetType="{x:Type xcdg:HierarchicalGroupByControl}">
<Setter Property="NoGroupContent"
      Value="Hello World" />
</Style>
Greetings
Gregor Glinka

Created Unassigned: WindowContainer [19756]

$
0
0
I have a Window with the following contents connected to a view model with a bool "IsOpen" property defaulted to false.

```
<Grid>
<TextBox Text="Background Control" Height="28" HorizontalAlignment="Left" Margin="112,106,0,0" VerticalAlignment="Top" />
<primitive:WindowContainer ModalBackgroundBrush="#70000000">
<control:ChildWindow IsModal="true" WindowStartupLocation="Center" WindowState="{Binding IsOpen, Converter={StaticResource BoolToState}}">
<TextBlock Text="Text" />
</control:ChildWindow>
</primitive:WindowContainer>
</Grid>
```
When the Window opens, the ModalBackgroudnColor is shown and the background TextBox is not accessible.

I would expect that since the only ChildWindow is closed that the WindowContainer ModalBackgroundColor would not be visible.

If I toggle "IsOpen" or start with the property defaulted to true, the update to false has the WindowContainer vanishing properly.

Commented Unassigned: DoubleUpDown.IsEditable gone? [19754]

$
0
0
From discussion:
https://wpftoolkit.codeplex.com/discussions/444607

IsReadOnly property has replaced "IsEditable" since v1.6.
But the current property (IsReadOnly) disable all input.
The legacy behavior was to only disable text input, keeping the button spinner working.
(To confirm the legacy behavior with the keyboard arrows and mouse wheel)

We should have the option to prevent text input without preventing the user to spin.

Probably something like a "AllowTextInput" property.
Comments: ** Comment from web user: emartin **

In the meantime, a workaround would be to subclass DoubleUpDown and force the IsReadOnly of the textbox:

```
public class MyDoubleUpDown : DoubleUpDown
{
public override void OnApplyTemplate()
{
base.OnApplyTemplate();
if( this.TextBox != null )
{
this.TextBox.IsReadOnly = true;
}
}
}
```

New Post: DoubleUpDown.IsEditable gone?

$
0
0
A workaround have been added to the issue comments

New Post: Hex TextBox

$
0
0
Hi,
I'd like to have a Hex text box with the leading "0x" using one of the Extended WPF Toolkit controls (with DataBinding).
Is there any control on the toolkit that supports this behavior?
If so, I'd appreciate a sample code of how to achieve this behavior.

Thanks!

Updated Wiki: Home

$
0
0
Just Launched! Community Edition v2.0.0 released with 67 improvements (see list). The Plus Edition gets 10 additional improvements and new controls. 25% rebate coupon'LAUNCH20B' until May 31 at shop.

Extended WPF Toolkit Plus

Extended WPF Toolkit™ is the number one collection of WPF controls, components and utilities for creating next generation Windows applications. Use it to build professional looking, modern, and easy to use line of business applications. The Extended WPF Toolkit project has been downloaded more than 200,000 times here and on Nuget.

The free, open source Community Edition is provided under the Microsoft Public License and includes the following controls:

AvalonDocknew in 2.0AutoSelectTextBoxBusyIndicatorButtonSpinner
CalculatorCalculatorUpDownCheckComboBoxCheckListBox
ChildWindownew featuresCollectionEditorDataGridCollectionControlDialog
ColorCanvasColorPickerDateTimePickerDateTimeUpDown
DecimalUpDownDoubleUpDownDropDownButtonIntegerUpDown
MagnifierMaskedTextBoxMessageBoxnew featuresMultiLineTextEditor
PiePrimitiveTypeCollEditorPropertyGridnew featuresRichTextBox
RichTextBoxFormatBarSplitButtonPanels/Layoutsnew in 1.9TimelinePanel
TimePickerWatermarkTextBoxWindowContainernew in 2.0 WindowControl new in 2.0
Windows 8 Theme new in 2.0WizardZoombox

Upgrade to Extended WPF Toolkit Plus to get even more controls, features, and professional support.

Latest News

New Live Explorer app available online as a Click Once app. Try it now!.

May 21st 2013 released Community Edition v2.0.0 containing 67 new improvements (see list).

 
Extended WPF Toolkit PlusMay 7th 2013 released Plus Edition v2.0.0 containing a variety of new controls and enhancements, including a styleable and feature-rich Chart control.

Jan 28th 2013 released v1.9.0 of the Community Edition, the first update this year. It contains a record-breaking 70 improvements (see the complete list) and a new control.

Action items

  • Enjoy WPF!
  • Please rate this release and write something positive. It's at the bottom of the downloads page
  • Follow this project (click "follow" at the top right of this page)
  • Follow @datagrid on Twitter for WPF and Toolkit news
  • Like Xceed's WPF page on Facebook
  • Check out a video or two on XceedVideos YouTube Channel
  • Add bugs or feature requests to the Issue Tracker

MCC11_Logo_Horizontal_Full-color.jpg

Updated Wiki: Home

$
0
0
Just Launched! Community Edition v2.0.0 released with 67 improvements (see list). The Plus Edition gets 10 additional improvements and new controls. 25% rebate coupon'LAUNCH20B' until May 31 at shop.

Extended WPF Toolkit Plus

Extended WPF Toolkit™ is the number one collection of WPF controls, components and utilities for creating next generation Windows applications. Use it to build professional looking, modern, and easy to use line of business applications. The Extended WPF Toolkit project has been downloaded more than 200,000 times here and on Nuget.

The free, open source Community Edition is provided under the Microsoft Public License and includes the following controls:

AvalonDocknew in 2.0AutoSelectTextBoxBusyIndicatorButtonSpinner
CalculatorCalculatorUpDownCheckComboBoxCheckListBox
ChildWindownew featuresCollectionEditorDataGridCollectionControlDialog
ColorCanvasColorPickerDateTimePickerDateTimeUpDown
DecimalUpDownDoubleUpDownDropDownButtonIntegerUpDown
MagnifierMaskedTextBoxMessageBoxnew featuresMultiLineTextEditor
PiePrimitiveTypeCollEditorPropertyGridnew featuresRichTextBox
RichTextBoxFormatBarSplitButtonPanels/Layoutsnew in 1.9TimelinePanel
TimePickerWatermarkTextBoxWindowContainernew in 2.0 WindowControl new in 2.0
Windows 8 Theme new in 2.0WizardZoombox

Upgrade to Extended WPF Toolkit Plus to get even more controls, features, and professional support.

Latest News

New Live Explorer app available online as a Click Once app. Try it now!.

May 21st 2013 released Community Edition v2.0.0 containing 67 new improvements (see list).

 
Extended WPF Toolkit PlusMay 7th 2013 released Plus Edition v2.0.0 containing a variety of new controls and enhancements, including a styleable and feature-rich Chart control.

Jan 28th 2013 released v1.9.0 of the Community Edition, the first update this year. It contains a record-breaking 70 improvements (see the complete list) and a new control.

Action items

  • Enjoy WPF!
  • Please rate this release and write something positive. It's at the bottom of the downloads page
  • Follow this project (click "follow" at the top right of this page)
  • Follow @datagrid on Twitter for WPF and Toolkit news
  • Like Xceed's WPF page on Facebook
  • Check out a video or two on XceedVideos YouTube Channel
  • Add bugs or feature requests to the Issue Tracker

MCC11_Logo_Horizontal_Full-color.jpg

Created Unassigned: CheckListBox.SelectedItemChanged event does not exist but ItemSelectionChanged does [19759]

$
0
0
In version 1.9.0, the documented CheckListBox.SelectedItemChanged event does not exist. However, there is a ItemSelectionChanged event.

http://wpftoolkit.codeplex.com/wikipage?title=CheckListBox&referringTitle=Documentation

New Comment on "Improvements200"


New Post: Please Help

$
0
0
HOw can I implement [Category("Information")] in vb.net.... I think something in bracket. How can I use it in vb.net class????

New Post: How to change error template of propertygrid elements

$
0
0
Hi,

Is case of error, by default there is a red border and we can show the error from the tooltip. I would like to show the error directly under the composant in a textblock.

Thanks.

New Post: Prevent DataGridControl Cell getting focus?

$
0
0
Hi,

I'm evaluating whether our team should switch from the WPF DataGrid to the Xceed DataGridControl Community Edition. One part of the evaluation is whether we can drop some attached behaviors written for the WPF DataGrid.

One of the behaviors prevents that a cell is getting the focus. It so possible to accomplish "out of the box" or did we still need a custom behavior (or even a derived DataGridControl)? I didn't find a way by my self.

Thanks in advance,
Carsten

Updated Wiki: Documentation

$
0
0

Controls

Installation and Usage Instructions

Please note: The Extended WPF Toolkit is dependent on .NET Framework 4.0. You must install .NET Framework 4.0 in order to use any features in the Toolkit.

Instructions for using the Extended WPF Toolkit binaries:

  1. Install .NET Framework 4.0.
  2. Download the ExtendedWPFToolkit_Binaries
  3. Unblock the ZIP file.
    1. Right-click ExtendedWPFToolkit_Binaries.zip -> Properties -> Unblock
  4. Unzip the ExtendedWPFToolkit_Binaries.zip
  5. Reference the binaries in your project:
    1. Reference WPFToolkit.Extended.dll in your project (Xceed.Wpf.DataGrid.dll for the datagrid control)
    2. Add a using statement ("using Xceed.Wpf.Toolkit;" for most of the controls, "using Xceed.Wpf.DataGrid;" for the datagrid control) to the top of .cs files
    3. Add a new xmlns (xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit" for most of the controls, xmlns:xcdg="http://schemas.xceed.com/wpf/xaml/datagrid" for the datagrid control) to the top of XAML files
    4. Remember to use the namespace prefix (in the above example, <xctk: ...> or <xcdg: ...>) in the body of your XAML

Installation using NuGet

  1. Install NuGet (can be downloaded for this link).
  2. Open your Visual Studio.
  3. Open your solution/project.
  4. Open Tools menu, select Library Package Manager and select Package Manager Console
  5. Run the following command Install-Package Extended.Wpf.Toolkit
    1. Add a using statement ("using Xceed.Wpf.Toolkit;" for most of the controls, "using Xceed.Wpf.DataGrid;" for the datagrid control) to the top of .cs files
    2. Add a new xmlns (xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit" for most of the controls, xmlns:xcdg="http://schemas.xceed.com/wpf/xaml/datagrid" for the datagrid control) to the top of XAML files
    3. Remember to use the namespace prefix (in the above example, <xctk: ...> or <xcdg: ...>) in the body of your XAML


Created Unassigned: [IntegerUpDown] InvalidOperationException thrown on double-click when IsEnabled=false [19762]

$
0
0
If you double-click on an IntegerUpDown when it is disabled, it will throw an InvalidOperationException stating: 'EditItem' is not allowed for this view.

Steps:
1. On an IntegerUpDown control in XAML, set IsEnabled="False" on the control.
2. Run your application in debug mode.
3. In the window that contains the control, double-click on the control. Observe the exception that is thrown.

I was using both IsEnable=false and IsReadOnly=true when I stumbled upon this bug. IsReadOnly=true allows the control to not be edited, and IsEnabled=false grays out the control. You only need to set IsEnabled=false to reproduce this bug. I believe it is a valid configuration to want the control set to read only AND have it grayed out. If it is grayed out, it tells the user it cannot be edited.
Viewing all 4964 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>