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

Updated Wiki: Home

June 14, 2016, 12:55 pm
$
0
0
June 14, 2016: Three months, three major releases of the Community Edition. Hot on the heels of last month's 2.8.0 update, Community Edition v2.9.0 has been released with 32 bug fixes and improvements. Users of the Plus Edition received v3.0.0 on April 6, 2016 with 2 new controls and 41 bug fixes and improvements.

June 9 to June 24, 2016: $100 off Toolkit Plus with coupon 'jetfuel' sunglass-emoji.png

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 500,000 times here and on NuGet.

The free, open source Community Edition is provided under the Microsoft Public License. The Plus Edition adds additional controls and features, and is at least one release version ahead. Get it with a subscription to also get updates and email support for 1 year. The Business Suite for WPF adds the full-featured version of the industry's best datagrid.

Controls included in the Community Edition:

AvalonDockAutoSelectTextBoxBusyIndicatorButtonSpinner
ByteUpDownCalculatorCalculatorUpDownCheckComboBox
CheckListBoxChildWindowCollectionControlCollectionControlDialog
ColorCanvasColorPickerDataGridDateTimePicker
DateTimeUpDownDecimalUpDownDoubleUpDownDropDownButton
IntegerUpDownLongUpDownMagnifierMaskedTextBox
MessageBoxMultiLineTextEditorPieChartPrimitiveTypeCollEditor
PropertyGridRangeSliderRichTextBoxRichTextBoxFormatBar
ShortUpDownSingleUpDownSplitButtonSwitchPanel
TimelinePanelTimePickerTimeSpanUpDownValueRangeTextBox
WatermarkTextBoxWatermarkComboBoxWindowContainerWindowControl
WizardZoombox Windows 8 Theme

Additional controls and features in the Plus Edition:

ChartsChildWindow PlusFilePicker PlusMaterial Design controls
MessageBox PlusMultiCalendarMultiColumnComboBoxPileFlowPanel
PropertyGrid PlusRadialGaugeRatingSlideShow
StyleableWindowSwitchPanel PlusToggleSwitchTokenizedTextBox
Ultimate ListBoxWatermarkPasswordBoxWindowControl Plus
Metro theme Office theme Technical support 1+ release ahead

Additional controls and features in the Business Suite for WPF:

Advanced DataGrid 3D Views for WPF More themes

Latest News

 
Bitcoin You can purchase the Plus Edition with bitcoins. Just visit this page, select the license type and quantity, then later select Bitcoin in the payment options.

 
Xceed Toolkit Plus for WPF

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

community-full.png
↧
Search

Updated Wiki: Home

June 14, 2016, 12:57 pm
$
0
0
June 14, 2016: Three months, three major releases of the Community Edition. Hot on the heels of last month's 2.8.0 update, Community Edition v2.9.0 has been released with 32 bug fixes and improvements. Users of the Plus Edition received v3.0.0 on April 5, 2016 with 2 new controls and 41 bug fixes and improvements.

June 9 to June 24, 2016: $100 off Toolkit Plus with coupon 'jetfuel' sunglass-emoji.png

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 500,000 times here and on NuGet.

The free, open source Community Edition is provided under the Microsoft Public License. The Plus Edition adds additional controls and features, and is at least one release version ahead. Get it with a subscription to also get updates and email support for 1 year. The Business Suite for WPF adds the full-featured version of the industry's best datagrid.

Controls included in the Community Edition:

AvalonDockAutoSelectTextBoxBusyIndicatorButtonSpinner
ByteUpDownCalculatorCalculatorUpDownCheckComboBox
CheckListBoxChildWindowCollectionControlCollectionControlDialog
ColorCanvasColorPickerDataGridDateTimePicker
DateTimeUpDownDecimalUpDownDoubleUpDownDropDownButton
IntegerUpDownLongUpDownMagnifierMaskedTextBox
MessageBoxMultiLineTextEditorPieChartPrimitiveTypeCollEditor
PropertyGridRangeSliderRichTextBoxRichTextBoxFormatBar
ShortUpDownSingleUpDownSplitButtonSwitchPanel
TimelinePanelTimePickerTimeSpanUpDownValueRangeTextBox
WatermarkTextBoxWatermarkComboBoxWindowContainerWindowControl
WizardZoombox Windows 8 Theme

Additional controls and features in the Plus Edition:

ChartsChildWindow PlusFilePicker PlusMaterial Design controls
MessageBox PlusMultiCalendarMultiColumnComboBoxPileFlowPanel
PropertyGrid PlusRadialGaugeRatingSlideShow
StyleableWindowSwitchPanel PlusToggleSwitchTokenizedTextBox
Ultimate ListBoxWatermarkPasswordBoxWindowControl Plus
Metro theme Office theme Technical support 1+ release ahead

Additional controls and features in the Business Suite for WPF:

Advanced DataGrid 3D Views for WPF More themes

Latest News

 
Bitcoin You can purchase the Plus Edition with bitcoins. Just visit this page, select the license type and quantity, then later select Bitcoin in the payment options.

 
Xceed Toolkit Plus for WPF

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

community-full.png
↧
↧

Updated Wiki: Home

June 14, 2016, 12:59 pm
$
0
0
June 14, 2016: Three months, three major releases of the Community Edition. Hot on the heels of last month's 2.8.0 update, Community Edition v2.9.0 has been released with 32 bug fixes and improvements. Users of the Plus Edition received v3.0.0 on April 5, 2016 with 2 new controls and 41 bug fixes and improvements. Plus Edition v3.1 coming in July.

June 9 to June 24, 2016: $100 off Toolkit Plus with coupon 'jetfuel' sunglass-emoji.png

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 500,000 times here and on NuGet.

The free, open source Community Edition is provided under the Microsoft Public License. The Plus Edition adds additional controls and features, and is at least one release version ahead. Get it with a subscription to also get updates and email support for 1 year. The Business Suite for WPF adds the full-featured version of the industry's best datagrid.

Controls included in the Community Edition:

AvalonDockAutoSelectTextBoxBusyIndicatorButtonSpinner
ByteUpDownCalculatorCalculatorUpDownCheckComboBox
CheckListBoxChildWindowCollectionControlCollectionControlDialog
ColorCanvasColorPickerDataGridDateTimePicker
DateTimeUpDownDecimalUpDownDoubleUpDownDropDownButton
IntegerUpDownLongUpDownMagnifierMaskedTextBox
MessageBoxMultiLineTextEditorPieChartPrimitiveTypeCollEditor
PropertyGridRangeSliderRichTextBoxRichTextBoxFormatBar
ShortUpDownSingleUpDownSplitButtonSwitchPanel
TimelinePanelTimePickerTimeSpanUpDownValueRangeTextBox
WatermarkTextBoxWatermarkComboBoxWindowContainerWindowControl
WizardZoombox Windows 8 Theme

Additional controls and features in the Plus Edition:

ChartsChildWindow PlusFilePicker PlusMaterial Design controls
MessageBox PlusMultiCalendarMultiColumnComboBoxPileFlowPanel
PropertyGrid PlusRadialGaugeRatingSlideShow
StyleableWindowSwitchPanel PlusToggleSwitchTokenizedTextBox
Ultimate ListBoxWatermarkPasswordBoxWindowControl Plus
Metro theme Office theme Technical support 1+ release ahead

Additional controls and features in the Business Suite for WPF:

Advanced DataGrid 3D Views for WPF More themes

Latest News

 
Bitcoin You can purchase the Plus Edition with bitcoins. Just visit this page, select the license type and quantity, then later select Bitcoin in the payment options.

 
Xceed Toolkit Plus for WPF

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

community-full.png
↧

Updated Release: Extended WPF Toolkit - 2.9.0 (Jun 14, 2016)

June 14, 2016, 12:59 pm
$
0
0

What's new in v2.9 Community Edition? (Released June 14, 2016)

  • Three months, three major releases of the Community Edition. Hot on the heels of last month's update, v2.9.0 contains 32 bug fixes and improvements (See the complete list of improvements in v2.9.0).
  • Plus Edition updated to v3.0 on April 5, 2016 with 2 new controls and 41 bug fixes and improvements. Support the project, and get more features.
  • Plus Edition v3.1 coming in July.

Want an easier way to install the Extended WPF Toolkit?

The Extended WPF Toolkit is available on NuGet. (Available as of June 17 2016.)

.NET Framework notes:

Requires .NET Framework 4.0, 4.5 or 4.6. A build for .NET 3.5 is available but also requires the WPFToolkit to be installed.

Instructions for using the Extended WPF Toolkit binaries:

  1. Install .NET Framework 4.0/4.5/4.6
  2. Download the ExtendedWPFToolkit_Binaries
  3. Right-click ExtendedWPFToolkit_Binaries.zip -> Properties -> Unblock
  4. Unzip the ExtendedWPFToolkit_Binaries.zip
  5. Add a using statement ("using Xceed.Wpf.Toolkit;") to the top of .cs files
  6. Add a new xmlns (for example, xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit") to the top of XAML files
  7. In your XAML, use the namespace prefix (in the above example, <xctk: ...>)
↧

Released: Extended WPF Toolkit - 2.9.0 (Jun 14, 2016)

June 14, 2016, 1:01 pm
$
0
0

What's new in v2.9 Community Edition? (Released June 14, 2016)

  • Three months, three major releases of the Community Edition. Hot on the heels of last month's update, v2.9.0 contains 32 bug fixes and improvements (See thecomplete list of improvements in v2.9.0).
  • Plus Edition updated to v3.0 on April 5, 2016 with 2 new controls and 41 bug fixes and improvements. Support the project,and get more features.
  • Plus Edition v3.1 coming in July.
  • Check project home page for coupon for the Plus Edition until June 24, 2016

Want an easier way to install the Extended WPF Toolkit?

The Extended WPF Toolkit is available on NuGet. (Available as of June 17 2016.)

.NET Framework notes:

Requires .NET Framework 4.0, 4.5 or 4.6. A build for .NET 3.5 is available but also requires the WPFToolkit to be installed.

Instructions for using the Extended WPF Toolkit binaries:

  1. Install .NET Framework 4.0/4.5/4.6
  2. Download the ExtendedWPFToolkit_Binaries
  3. Right-click ExtendedWPFToolkit_Binaries.zip -> Properties -> Unblock
  4. Unzip the ExtendedWPFToolkit_Binaries.zip
  5. Add a using statement ("using Xceed.Wpf.Toolkit;") to the top of .cs files
  6. Add a new xmlns (for example, xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit") to the top of XAML files
  7. In your XAML, use the namespace prefix (in the above example, <xctk: ...>)
↧
↧

Updated Release: Extended WPF Toolkit - 2.9.0 (Jun 14, 2016)

June 14, 2016, 1:01 pm
$
0
0

What's new in v2.9 Community Edition? (Released June 14, 2016)

  • Three months, three major releases of the Community Edition. Hot on the heels of last month's update, v2.9.0 contains 32 bug fixes and improvements (See the complete list of improvements in v2.9.0).
  • Plus Edition updated to v3.0 on April 5, 2016 with 2 new controls and 41 bug fixes and improvements. Support the project, and get more features.
  • Plus Edition v3.1 coming in July.
  • Check project home page for coupon for the Plus Edition until June 24, 2016

Want an easier way to install the Extended WPF Toolkit?

The Extended WPF Toolkit is available on NuGet. (Available as of June 17 2016.)

.NET Framework notes:

Requires .NET Framework 4.0, 4.5 or 4.6. A build for .NET 3.5 is available but also requires the WPFToolkit to be installed.

Instructions for using the Extended WPF Toolkit binaries:

  1. Install .NET Framework 4.0/4.5/4.6
  2. Download the ExtendedWPFToolkit_Binaries
  3. Right-click ExtendedWPFToolkit_Binaries.zip -> Properties -> Unblock
  4. Unzip the ExtendedWPFToolkit_Binaries.zip
  5. Add a using statement ("using Xceed.Wpf.Toolkit;") to the top of .cs files
  6. Add a new xmlns (for example, xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit") to the top of XAML files
  7. In your XAML, use the namespace prefix (in the above example, <xctk: ...>)
↧

New Post: Set property min/max in PropertyGrid without multiple editors?

June 14, 2016, 7:31 pm
$
0
0
Fantastic.
Definitely looking forward to v3.0, looks like it has a lot of useful features.

Thanks!
↧

New Comment on "DateTimePicker"

June 15, 2016, 9:15 am
$
0
0
Hi, you can try to set the DefaultValue property.
↧
Search

Created Unassigned: AvalonDock DocumentsSource binding cause memory leak [22293]

June 16, 2016, 9:55 am
$
0
0
After I update AvalonDock to Ver.3.0.16174.17450, I've got memory leak.
It occurs even in the simplest case.
(only binding DocumentsSoure with ObservableCollection<object>)
Here are some screenshot to show what is happened.

1st image shows after my test app launched. It took only 2MB.
2nd image shows after add some documents. It took 21MB and GC can't reduce this, but it's OK.
3rd image shows after I delete all documents and run GC. It still took 21MB.
![Image](http://i.imgur.com/g9NBSTt.png)
![Image](http://i.imgur.com/RQvZmKa.png)
![Image](http://i.imgur.com/IAwvcLm.png)

And if I repeat this process, test app devours RAM.
Attached project is test app in screen shot.

I think this is critical bug, please check and fix this ASAP.

Cheers.
↧
↧

Commented Unassigned: AvalonDock DocumentsSource binding cause memory leak [22293]

June 16, 2016, 12:56 pm
$
0
0
After I update AvalonDock to Ver.3.0.16174.17450, I've got memory leak.
It occurs even in the simplest case.
(only binding DocumentsSoure with ObservableCollection<object>)
Here are some screenshot to show what is happened.

1st image shows after my test app launched. It took only 2MB.
2nd image shows after add some documents. It took 21MB and GC can't reduce this, but it's OK.
3rd image shows after I delete all documents and run GC. It still took 21MB.
![Image](http://i.imgur.com/g9NBSTt.png)
![Image](http://i.imgur.com/RQvZmKa.png)
![Image](http://i.imgur.com/IAwvcLm.png)

And if I repeat this process, test app devours RAM.
Attached project is test app in screen shot.

I think this is critical bug, please check and fix this ASAP.

Cheers.
Comments: ** Comment from web user: BoucherS **

Hi,

Make sure you remove the DocumentViewModels when they are removed from the DockingManager :

```
<ad:DockingManager Grid.Row="1"
DocumentsSource="{Binding Documents, Mode=OneTime}"
DocumentClosed="DockingManager_DocumentClosed">
</ad:DockingManager>
```
```
private void DockingManager_DocumentClosed( object sender, Xceed.Wpf.AvalonDock.DocumentClosedEventArgs e )
{
var workspace = this.DataContext as WorkspaceViewModel;
workspace.Documents.Remove( e.Document.Content );
}
```

This way, doing a "GC" will clear some memory.

↧

Created Unassigned: DateTimePicker seems broken on new build [22295]

June 17, 2016, 8:58 pm
$
0
0
Hello.

I just wanted to report an issue that I encountered today when I updated my nuget packet to the new build.

I have an application that I've had developed for quite a while that used the DateTimePicker as part of search criteria in an MVVM light viewmodel. It worked fine until I updated the package.

I downloaded and referenced the 2.8 libraries and things worked again. So, i'm unsure if something changed that perhaps I am violating, or there may be an issue.

For reference, in my viewmodel I have a property defined as below:

```
private DateTime? _createdAfter = null;
public DateTime? CreatedAfter
{
get
{
if (IsInDesignMode) { return new DateTime(2012, 12, 12); }
else { return _createdAfter; }
}
set
{
if (_createdAfter != value)
{
_createdAfter = value;
RaisePropertyChanged(() => CreatedAfter);
}
}
}
```

Bound to the DateTimePicker as thus:
```

<xctk:DateTimePicker Format="Custom" Value="{Binding CreatedAfter, Mode=TwoWay}" />
```

After updating I got the following error:

__Index was out of range. Must be non-negative and less than the size of the collection.__

with this stack trace error:

at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at Xceed.Wpf.Toolkit.DateTimeUpDown.OnValueChanged(Nullable`1 oldValue, Nullable`1 newValue)
at Xceed.Wpf.Toolkit.DateTimePicker.OnValueChanged(Nullable`1 oldValue, Nullable`1 newValue)
at Xceed.Wpf.Toolkit.Primitives.UpDownBase`1.OnValueChanged(DependencyObject o, DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.DependencyObject.ClearValueCommon(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata)
at System.Windows.DependencyObject.ClearValue(DependencyProperty dp)
↧

Commented Unassigned: AvalonDock DocumentsSource binding cause memory leak [22293]

June 19, 2016, 4:03 pm
$
0
0
After I update AvalonDock to Ver.3.0.16174.17450, I've got memory leak.
It occurs even in the simplest case.
(only binding DocumentsSoure with ObservableCollection<object>)
Here are some screenshot to show what is happened.

1st image shows after my test app launched. It took only 2MB.
2nd image shows after add some documents. It took 21MB and GC can't reduce this, but it's OK.
3rd image shows after I delete all documents and run GC. It still took 21MB.
![Image](http://i.imgur.com/g9NBSTt.png)
![Image](http://i.imgur.com/RQvZmKa.png)
![Image](http://i.imgur.com/IAwvcLm.png)

And if I repeat this process, test app devours RAM.
Attached project is test app in screen shot.

I think this is critical bug, please check and fix this ASAP.

Cheers.
Comments: ** Comment from web user: hyge **

You're right, I've forgot to remove Document from collections...Sorry for lack of confirmaion.

But if I add "Remove" command in MVVM fashion, there is another issue.
To remove Document from collection, AvalonDock throws NullReferenceException.
Here is some snippet.

```
var workspace = this.DataContext as WorkspaceViewModel;
if (workspace.Documents.Count > 0)
workspace.Documents.RemoveAt(workspace.Documents.Count - 1); //NullReferenceException is thrown.
```

If I "activate" document to close by select it, exception not thrown.

Am I missing something again?
Attached project repro this behavior.
"Add" twice or more and "Remove", then, Exeption thrown.

And maybe Michael_Brave reported [here](https://avalondock.codeplex.com/workitem/17673) is the same issue.

Regards.

↧

Commented Unassigned: AvalonDock DocumentsSource binding cause memory leak [22293]

June 20, 2016, 5:49 am
$
0
0
After I update AvalonDock to Ver.3.0.16174.17450, I've got memory leak.
It occurs even in the simplest case.
(only binding DocumentsSoure with ObservableCollection<object>)
Here are some screenshot to show what is happened.

1st image shows after my test app launched. It took only 2MB.
2nd image shows after add some documents. It took 21MB and GC can't reduce this, but it's OK.
3rd image shows after I delete all documents and run GC. It still took 21MB.
![Image](http://i.imgur.com/g9NBSTt.png)
![Image](http://i.imgur.com/RQvZmKa.png)
![Image](http://i.imgur.com/IAwvcLm.png)

And if I repeat this process, test app devours RAM.
Attached project is test app in screen shot.

I think this is critical bug, please check and fix this ASAP.

Cheers.
Comments: ** Comment from web user: BoucherS **

Hi,

This is already fixed. The fix will be included in release : v3.1.

In the meantime, here's what you can do ;
1) In file Xceed.Wpf.AvalonDock/Controls/LayoutItem.cs,
add the following method :
internal bool IsViewExists()
{
return (_view != null);
}
2)In file Xceed.Wpf.AvalonDock/DockingManager.cs,
In method : RemoveViewFromLogicalChild,
Replace :
this.InternalRemoveLogicalChild( layoutItem.View );
with :
if( layoutItem.IsViewExists() )
{
this.InternalRemoveLogicalChild( layoutItem.View );
}

↧
↧

Edited Issue: AvalonDock DocumentsSource binding cause memory leak [22293]

June 20, 2016, 5:49 am
$
0
0
After I update AvalonDock to Ver.3.0.16174.17450, I've got memory leak.
It occurs even in the simplest case.
(only binding DocumentsSoure with ObservableCollection<object>)
Here are some screenshot to show what is happened.

1st image shows after my test app launched. It took only 2MB.
2nd image shows after add some documents. It took 21MB and GC can't reduce this, but it's OK.
3rd image shows after I delete all documents and run GC. It still took 21MB.
![Image](http://i.imgur.com/g9NBSTt.png)
![Image](http://i.imgur.com/RQvZmKa.png)
![Image](http://i.imgur.com/IAwvcLm.png)

And if I repeat this process, test app devours RAM.
Attached project is test app in screen shot.

I think this is critical bug, please check and fix this ASAP.

Cheers.
↧

Commented Unassigned: DateTimePicker seems broken on new build [22295]

June 20, 2016, 6:56 am
$
0
0
Hello.

I just wanted to report an issue that I encountered today when I updated my nuget packet to the new build.

I have an application that I've had developed for quite a while that used the DateTimePicker as part of search criteria in an MVVM light viewmodel. It worked fine until I updated the package.

I downloaded and referenced the 2.8 libraries and things worked again. So, i'm unsure if something changed that perhaps I am violating, or there may be an issue.

For reference, in my viewmodel I have a property defined as below:

```
private DateTime? _createdAfter = null;
public DateTime? CreatedAfter
{
get
{
if (IsInDesignMode) { return new DateTime(2012, 12, 12); }
else { return _createdAfter; }
}
set
{
if (_createdAfter != value)
{
_createdAfter = value;
RaisePropertyChanged(() => CreatedAfter);
}
}
}
```

Bound to the DateTimePicker as thus:
```

<xctk:DateTimePicker Format="Custom" Value="{Binding CreatedAfter, Mode=TwoWay}" />
```

After updating I got the following error:

__Index was out of range. Must be non-negative and less than the size of the collection.__

with this stack trace error:

at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at Xceed.Wpf.Toolkit.DateTimeUpDown.OnValueChanged(Nullable`1 oldValue, Nullable`1 newValue)
at Xceed.Wpf.Toolkit.DateTimePicker.OnValueChanged(Nullable`1 oldValue, Nullable`1 newValue)
at Xceed.Wpf.Toolkit.Primitives.UpDownBase`1.OnValueChanged(DependencyObject o, DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.DependencyObject.ClearValueCommon(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata)
at System.Windows.DependencyObject.ClearValue(DependencyProperty dp)
Comments: ** Comment from web user: BoucherS **

Hi,

Thanks for your feedback.

Make sure that when you use the DateTimePicker.Format property to "Custom", you also set a value for property DateTimePicker.FormatString.

↧
Search

Commented Unassigned: DateTimePicker seems broken on new build [22295]

June 20, 2016, 6:58 am
$
0
0
Hello.

I just wanted to report an issue that I encountered today when I updated my nuget packet to the new build.

I have an application that I've had developed for quite a while that used the DateTimePicker as part of search criteria in an MVVM light viewmodel. It worked fine until I updated the package.

I downloaded and referenced the 2.8 libraries and things worked again. So, i'm unsure if something changed that perhaps I am violating, or there may be an issue.

For reference, in my viewmodel I have a property defined as below:

```
private DateTime? _createdAfter = null;
public DateTime? CreatedAfter
{
get
{
if (IsInDesignMode) { return new DateTime(2012, 12, 12); }
else { return _createdAfter; }
}
set
{
if (_createdAfter != value)
{
_createdAfter = value;
RaisePropertyChanged(() => CreatedAfter);
}
}
}
```

Bound to the DateTimePicker as thus:
```

<xctk:DateTimePicker Format="Custom" Value="{Binding CreatedAfter, Mode=TwoWay}" />
```

After updating I got the following error:

__Index was out of range. Must be non-negative and less than the size of the collection.__

with this stack trace error:

at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at Xceed.Wpf.Toolkit.DateTimeUpDown.OnValueChanged(Nullable`1 oldValue, Nullable`1 newValue)
at Xceed.Wpf.Toolkit.DateTimePicker.OnValueChanged(Nullable`1 oldValue, Nullable`1 newValue)
at Xceed.Wpf.Toolkit.Primitives.UpDownBase`1.OnValueChanged(DependencyObject o, DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.DependencyObject.ClearValueCommon(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata)
at System.Windows.DependencyObject.ClearValue(DependencyProperty dp)
Comments: ** Comment from web user: BoucherS **

In v3.2, the DateTimePicker will throw if the FormatString property is null when Format property is set to "Custom".

↧

New Post: PropertyGrid error when opening collection

June 20, 2016, 1:08 pm
$
0
0
After upgrading to 2.9.0, I now get a "System.NullReferenceException" when I try to edit a List by clicking the "(Collection)" text in a PropertyGrid.
Reverting back to 2.8.0 fixes this.

The list is a System.Collections.Generic.List of a base class if that helps.
↧
↧

New Post: PropertyGrid error when opening collection

June 21, 2016, 5:20 am
$
0
0
Hi,

My first taught is that it is already fixed in later versions.
But just to make sure, can you submit a sample of the bug ?
When you say " edit a List by clicking the "(Collection)" text in a PropertyGrid", do you mean only clicking on the button, or actually editing the list in the CollectionEditor by modifying properties or adding/removing listBoxItems ?
What version of windows are you using ?

Thanks
↧

New Post: PropertyGrid error when opening collection

June 21, 2016, 12:44 pm
$
0
0
As soon as I click the "(Collection)" button to open a CollectionControlDialog, it will throw an exception.
It appears to be caused by having a List property inside of another List property.

Here is some code which will always throw a System.NullReferenceException.
If you initialise MyStringList via the constructor, it will throw a System.Reflection.TargetParameterCountException instead.
Removing the MyStringList property will stop all exceptions.
public MainWindow()
{
    InitializeComponent();
    PropertyGrid.SelectedObject = new MyContainerClass();
}
public class MyContainerClass
{
    public MyContainerClass()
    {
        MyClassList = new List<MyClass>();
        MyClassList.Add(new MyClass());
    }
    public List<MyClass> MyClassList { get; set; }
}
public class MyClass
{
    public List<string> MyStringList { get; set; }
}
The XAML for "PropertyGrid" is simply
<xctk:PropertyGrid x:Name="PropertyGrid" />
My Windows build version is 10586.420.
↧

New Post: Cannot close SplitButton dropdown using IsOpen property.

July 8, 2016, 10:40 am
$
0
0
Hi,

I tried the following code and the dropDown disappeared on each click of MenuItems, in v2.4, v2.9 and up.
<Window x:Class="WpfApplication93.MainWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:local="clr-namespace:WpfApplication93"
        xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit"
        mc:Ignorable="d"
        Title="MainWindow">
    <Grid>
      <xctk:SplitButton x:Name="MyButton"
                        Width="300"
                        Height="50"
                        Content="AddThing">
         <xctk:SplitButton.DropDownContent>
            <ItemsControl HorizontalAlignment="Left">
               <ItemsControl.Resources>
                  <Style TargetType="MenuItem">
                     <Setter Property="StaysOpenOnClick"
                              Value="False" />
                  </Style>
               </ItemsControl.Resources>
               <MenuItem Click="OnClickOne"
                           Header="AddThing" />
               <MenuItem Click="OnClickTwo"
                           Header="AddOtherThing" />
            </ItemsControl>
         </xctk:SplitButton.DropDownContent>
      </xctk:SplitButton>
   </Grid>
</Window>
namespace WpfApplication93
{
  public partial class MainWindow : Window
  {
    public MainWindow()
    {
      InitializeComponent();
    }

    private void OnClickOne( object sender, RoutedEventArgs e )
    {
      MyButton.IsOpen = false;
    }

    private void OnClickTwo( object sender, RoutedEventArgs e )
    {
      MyButton.IsOpen = false;
    }
  }
}
↧
Viewing all 4964 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>