Commented Unassigned: Cannot reference version 2.7.0 in Visual Studio 2010 [22246]

April 19, 2016, 9:31 am

≫ Next: Created Unassigned: DoubleUpDown Dependency Property Already Registered [22247]

≪ Previous: Created Unassigned: Cannot reference version 2.7.0 in Visual Studio 2010 [22246]

We have been using an older version specifically for the DateTimePicker. In needing some of the newer features, we tried using 2.7.0, but to no avail.

By adding a reference and pointing to the .dll, and adding a reference in xaml, it's not recognized and intellisense does not work. The following exception is also shown:

Unable to load the metadata for assembly 'Xceed.Wpf.Toolkit'. This assembly may have been downloaded from the web. See http://go.microsoft.com/fwlink/?LinkId=179545. The following error was encountered during load: Could not load file or assembly 'Xceed.Wpf.Toolkit, Version=2.6.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)

By trying to install via NuGet, it errors out stating it's not supported.

Any help is appreciated. Thank you...
Comments: ** Comment from web user: CrazyTasty **

Ignore the issue above. What I tried today seems to work fine.

Sorry for the confusion.

↧

Created Unassigned: DoubleUpDown Dependency Property Already Registered [22247]

April 19, 2016, 9:54 am

≫ Next: New Post: Set maximum value of TimeSpanUpDown

≪ Previous: Commented Unassigned: Cannot reference version 2.7.0 in Visual Studio 2010 [22246]

I am getting the following Xaml designer error when I use two different types of UpDown controls in the same document (In my case I have several IntegerUpDown controls and a DoubleUpDown). It seems that the dependency property is being registered multiple times, though it appears to be set up correctly as a static property in CommonNumericUpDown<T>. If I get rid of the DoubleUpDown control, the error goes away, but if I leave the DoubleUpDown and get rid of the IntegerUpDown controls instead, I get a similar error, but referencing the 'AutoMoveFocus' property (contained in UpDownBase<T>). This error doesn't prevent me from compiling and running my project just fine, but it does throw the error in the designer and prevent the design display from displaying my controls.

__Error__

Severity Code Description Project File Line Suppression State 'ParsingNumberStyle' property was already registered by 'Xceed_Wpf_Toolkit_CommonNumericUpDown`1_39_157692670'.

↧

New Post: Set maximum value of TimeSpanUpDown

April 19, 2016, 11:20 am

≫ Next: Commented Unassigned: DoubleUpDown Dependency Property Already Registered [22247]

≪ Previous: Created Unassigned: DoubleUpDown Dependency Property Already Registered [22247]

Hi. I'm trying to use the TimeSpanUpDown control and would like to limit the user to the 24 hour time format; so the user cannot enter days or seconds. Is it possible to only display hours and minutes? And keep the user from exceeding 23:59? Thanks.

↧

Commented Unassigned: DoubleUpDown Dependency Property Already Registered [22247]

April 23, 2016, 5:55 am

≫ Next: Updated Wiki: DataGrid

≪ Previous: New Post: Set maximum value of TimeSpanUpDown

I can reproduce it too. I'm using VS2015 Community. I have one IntegerUpDown two DateTimeUpDown controls.

↧

Updated Wiki: DataGrid

April 25, 2016, 6:17 am

≫ Next: Updated Wiki: DataGrid

≪ Previous: Commented Unassigned: DoubleUpDown Dependency Property Already Registered [22247]

DataGrid

The datagrid included in Extended WPF Toolkit provides a stunning, shaded appearance and capabilities such as inertial smooth scrolling and animated full-column reordering—which mimics the physics of real-life movement. Add to that the datagrid’s zero-lag data virtualization, and you have the fastest WPF datagrid around—in performance and feel. It also easily handles millions of rows and thousands of columns, and integrates quickly into any WPF app.

This datagrid was the first datagrid for WPF. It was released in 2007 and has been updated 68 times since then. It is used in many major business applications, and is also used by portions of Visual Studio.

The datagrid control is contained in a separate assembly, Xceed.Wpf.DataGrid, which must be added to your project and then referenced where necessary.

Note: You can find complete documentation of the API here. You can also find detailed descriptions of how the various classes work together in the Xceed DataGrid for WPF documentation, but please bear in mind that that product's documentation covers features that may not be available in this Toolkit version.

See the Advanced DataGrid page for a list of differences between the Toolkit's datagrid and the advanced edition, Xceed DataGrid for WPF.

Usage

XAML

<sample:DemoView x:Class="Samples.Modules.DataGrid.Views.HomeView"
                 xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
                 xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"  
                 xmlns:sample="clr-namespace:Samples.Infrastructure.Controls;assembly=Samples.Infrastructure"
                 xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit"
                 xmlns:xcdg="http://schemas.xceed.com/wpf/xaml/datagrid"
                 xmlns:compModel="clr-namespace:System.ComponentModel;assembly=WindowsBase"
                 xmlns:local="clr-namespace:Samples.Modules.DataGrid"
                 Title="DataGrid" 
                 x:Name="_demo">
    <sample:DemoView.Description>
        Extended WPF Toolkit DataGrid control sample.
    </sample:DemoView.Description>
    <Grid>
        <Grid.Resources>
            <xcdg:DataGridCollectionViewSource x:Key="cvsOrders"
                                            Source="{Binding ElementName=_demo, Path=Orders}">
                <xcdg:DataGridCollectionViewSource.GroupDescriptions>
                    <PropertyGroupDescription PropertyName="ShipCountry" />
                    <PropertyGroupDescription PropertyName="ShipCity" />
                </xcdg:DataGridCollectionViewSource.GroupDescriptions>
            </xcdg:DataGridCollectionViewSource>
        </Grid.Resources>

        <xcdg:DataGridControl x:Name="_dataGrid" 
                            MaxHeight="400"
                            ItemsSource="{Binding Source={StaticResource cvsOrders} }" >
            <xcdg:DataGridControl.View>
                <xcdg:TableflowView FixedColumnCount="2" />
            </xcdg:DataGridControl.View>

            <xcdg:DataGridControl.Columns>
                <!--Preconfigure the OrderID Column of the grid with CellValidationRule. -->
                <xcdg:Column FieldName="OrderID"
                         IsMainColumn="True">
                    <xcdg:Column.CellValidationRules>
                        <local:UniqueIDCellValidationRule />
                    </xcdg:Column.CellValidationRules>
                </xcdg:Column>
            </xcdg:DataGridControl.Columns>
        </xcdg:DataGridControl>
    </Grid>
</sample:DemoView>

Code behind

using Microsoft.Practices.Prism.Regions;
using Samples.Infrastructure.Controls;
using Xceed.Wpf.DataGrid.Samples.SampleData;
using System.Data;
using Xceed.Wpf.DataGrid;

namespace Samples.Modules.DataGrid.Views
{
  /// <summary>
  /// Interaction logic for HomeView.xaml
  /// </summary>
  [RegionMemberLifetime( KeepAlive = false )]
  public partial class HomeView : DemoView
  {
    public HomeView()
    {
      this.Orders = DataProvider.GetNorthwindDataSet().Tables[ "Orders" ];
      InitializeComponent();
    }

    public DataTable Orders
    {
      get;
      private set;
    }

  }
}

↧

Updated Wiki: DataGrid

April 25, 2016, 6:33 am

≫ Next: Updated Wiki: DataGrid

≪ Previous: Updated Wiki: DataGrid

DataGrid

The datagrid included in Extended WPF Toolkit provides a stunning, shaded appearance and capabilities such as inertial smooth scrolling and animated full-column reordering—which mimics the physics of real-life movement. Add to that the datagrid’s zero-lag data virtualization, and you have the fastest WPF datagrid around—in performance and feel. It also easily handles millions of rows and thousands of columns, and integrates quickly into any WPF app.

This datagrid was the first datagrid for WPF. It was released in 2007 and has been updated 68 times since then. It is used in many major business applications, and is also used by portions of Visual Studio.

The datagrid control is contained in a separate assembly, Xceed.Wpf.DataGrid, which must be added to your project and then referenced where necessary.

Note: You can find complete documentation of the datagrid API here. You can also find detailed descriptions of how the various classes work together in the Xceed DataGrid for WPF documentation, but please bear in mind that that product's documentation covers features that may not be available in this Toolkit version.

See the Advanced DataGrid page for a list of differences between the Toolkit's datagrid and the advanced edition, Xceed DataGrid for WPF.

Usage

XAML

<sample:DemoView x:Class="Samples.Modules.DataGrid.Views.HomeView"
                 xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
                 xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"  
                 xmlns:sample="clr-namespace:Samples.Infrastructure.Controls;assembly=Samples.Infrastructure"
                 xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit"
                 xmlns:xcdg="http://schemas.xceed.com/wpf/xaml/datagrid"
                 xmlns:compModel="clr-namespace:System.ComponentModel;assembly=WindowsBase"
                 xmlns:local="clr-namespace:Samples.Modules.DataGrid"
                 Title="DataGrid" 
                 x:Name="_demo">
    <sample:DemoView.Description>
        Extended WPF Toolkit DataGrid control sample.
    </sample:DemoView.Description>
    <Grid>
        <Grid.Resources>
            <xcdg:DataGridCollectionViewSource x:Key="cvsOrders"
                                            Source="{Binding ElementName=_demo, Path=Orders}">
                <xcdg:DataGridCollectionViewSource.GroupDescriptions>
                    <PropertyGroupDescription PropertyName="ShipCountry" />
                    <PropertyGroupDescription PropertyName="ShipCity" />
                </xcdg:DataGridCollectionViewSource.GroupDescriptions>
            </xcdg:DataGridCollectionViewSource>
        </Grid.Resources>

        <xcdg:DataGridControl x:Name="_dataGrid" 
                            MaxHeight="400"
                            ItemsSource="{Binding Source={StaticResource cvsOrders} }" >
            <xcdg:DataGridControl.View>
                <xcdg:TableflowView FixedColumnCount="2" />
            </xcdg:DataGridControl.View>

            <xcdg:DataGridControl.Columns>
                <!--Preconfigure the OrderID Column of the grid with CellValidationRule. -->
                <xcdg:Column FieldName="OrderID"
                         IsMainColumn="True">
                    <xcdg:Column.CellValidationRules>
                        <local:UniqueIDCellValidationRule />
                    </xcdg:Column.CellValidationRules>
                </xcdg:Column>
            </xcdg:DataGridControl.Columns>
        </xcdg:DataGridControl>
    </Grid>
</sample:DemoView>

Code behind

using Microsoft.Practices.Prism.Regions;
using Samples.Infrastructure.Controls;
using Xceed.Wpf.DataGrid.Samples.SampleData;
using System.Data;
using Xceed.Wpf.DataGrid;

namespace Samples.Modules.DataGrid.Views
{
  /// <summary>
  /// Interaction logic for HomeView.xaml
  /// </summary>
  [RegionMemberLifetime( KeepAlive = false )]
  public partial class HomeView : DemoView
  {
    public HomeView()
    {
      this.Orders = DataProvider.GetNorthwindDataSet().Tables[ "Orders" ];
      InitializeComponent();
    }

    public DataTable Orders
    {
      get;
      private set;
    }

  }
}

↧

Updated Wiki: DataGrid

April 25, 2016, 6:37 am

≫ Next: Updated Wiki: Advanced DataGrid

≪ Previous: Updated Wiki: DataGrid

DataGrid

The datagrid included in Extended WPF Toolkit provides a stunning, shaded appearance and capabilities such as inertial smooth scrolling and animated full-column reordering—which mimics the physics of real-life movement. Add to that the datagrid’s zero-lag data virtualization, and you have the fastest WPF datagrid around—in performance and feel. It also easily handles millions of rows and thousands of columns, and integrates quickly into any WPF app.

This datagrid was the first datagrid for WPF. It was released in 2007 and has been consistently updated since then. There have been 68 major and minor as of April 2016. It is used in many major business applications, and is also used by portions of Visual Studio.

The datagrid control is contained in a separate assembly, Xceed.Wpf.DataGrid, which must be added to your project and then referenced where necessary.

Note: You can find complete documentation of the datagrid API here. You can also find detailed descriptions of how the various classes work together in the Xceed DataGrid for WPF documentation, but please bear in mind that that product's documentation covers features that may not be available in this Toolkit version.

See the Advanced DataGrid page for a list of differences between the Toolkit's datagrid and the advanced edition, Xceed DataGrid for WPF.

Usage

XAML

<sample:DemoView x:Class="Samples.Modules.DataGrid.Views.HomeView"
                 xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
                 xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"  
                 xmlns:sample="clr-namespace:Samples.Infrastructure.Controls;assembly=Samples.Infrastructure"
                 xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit"
                 xmlns:xcdg="http://schemas.xceed.com/wpf/xaml/datagrid"
                 xmlns:compModel="clr-namespace:System.ComponentModel;assembly=WindowsBase"
                 xmlns:local="clr-namespace:Samples.Modules.DataGrid"
                 Title="DataGrid" 
                 x:Name="_demo">
    <sample:DemoView.Description>
        Extended WPF Toolkit DataGrid control sample.
    </sample:DemoView.Description>
    <Grid>
        <Grid.Resources>
            <xcdg:DataGridCollectionViewSource x:Key="cvsOrders"
                                            Source="{Binding ElementName=_demo, Path=Orders}">
                <xcdg:DataGridCollectionViewSource.GroupDescriptions>
                    <PropertyGroupDescription PropertyName="ShipCountry" />
                    <PropertyGroupDescription PropertyName="ShipCity" />
                </xcdg:DataGridCollectionViewSource.GroupDescriptions>
            </xcdg:DataGridCollectionViewSource>
        </Grid.Resources>

        <xcdg:DataGridControl x:Name="_dataGrid" 
                            MaxHeight="400"
                            ItemsSource="{Binding Source={StaticResource cvsOrders} }" >
            <xcdg:DataGridControl.View>
                <xcdg:TableflowView FixedColumnCount="2" />
            </xcdg:DataGridControl.View>

            <xcdg:DataGridControl.Columns>
                <!--Preconfigure the OrderID Column of the grid with CellValidationRule. -->
                <xcdg:Column FieldName="OrderID"
                         IsMainColumn="True">
                    <xcdg:Column.CellValidationRules>
                        <local:UniqueIDCellValidationRule />
                    </xcdg:Column.CellValidationRules>
                </xcdg:Column>
            </xcdg:DataGridControl.Columns>
        </xcdg:DataGridControl>
    </Grid>
</sample:DemoView>

Code behind

using Microsoft.Practices.Prism.Regions;
using Samples.Infrastructure.Controls;
using Xceed.Wpf.DataGrid.Samples.SampleData;
using System.Data;
using Xceed.Wpf.DataGrid;

namespace Samples.Modules.DataGrid.Views
{
  /// <summary>
  /// Interaction logic for HomeView.xaml
  /// </summary>
  [RegionMemberLifetime( KeepAlive = false )]
  public partial class HomeView : DemoView
  {
    public HomeView()
    {
      this.Orders = DataProvider.GetNorthwindDataSet().Tables[ "Orders" ];
      InitializeComponent();
    }

    public DataTable Orders
    {
      get;
      private set;
    }

  }
}

↧

Updated Wiki: Advanced DataGrid

April 25, 2016, 6:46 am

≫ Next: New Comment on "ChildWindow"

≪ Previous: Updated Wiki: DataGrid

Advanced DataGrid

The normal datagrid included in both the Community and Plus Edition of Extended WPF Toolkit is a rock-solid, high performance product with zero-lag data virtualization, the ability to handle large datasets, and with many core features. Xceed offers an advanced version of this datagrid with certain added features. You can purchase it separately, or try it for 45 days by clicking the 'Try it now' button here, but it is also included in the Xceed Business Suite for WPF as well.

The advanced version of the DataGrid includes the following additional features:

Master / Detail View

When a grid is in a table-view layout, its data items can display detail data that is usually provided by the detail descriptions defined in the DataGridCollectionView or DataGridCollectionViewSource to which the grid is bound. By default, detail descriptions are automatically created for most detail relation types; however, they can also be explicitly defined.

Tree Grid View

Represents a table-view layout similar to TableflowView, in which rows are laid out horizontally as in traditional grid-like styles, but detail columns are aligned with the columns of the master, and one column displays data using a tree-structure.

Like TableflowView, it provides animated smooth scrolling, sticky group headers and sticky master-detail master row and headers, full-column animated drag and drop reordering.

Card View

The CardView and CompactCardView classes provide card-view layouts for the data items in a grid. Either layout can be used to display data items as cards; however, the compact card-view layout applies well when a database has many columns but few of the fields contain data. In this case, the fields that do not contain data will not be displayed in the cards, giving them a more compact appearance.

3D View

The Cardflow™ 3D view, which is represented by the CardflowView3D class, provides a 3-dimensional card-view layout for the data items in a grid and allows various card "surfaces" to display data using customized, theme-defined surface configurations.

Filter Row

The FilterRow class represents a row in which values can be entered to filter the items in the corresponding columns. Custom type columns can also be filtered if they provide a TypeConverter (from string) and implement IComparable.

Insertion Row

The InsertionRow class represents a row in which values can be entered to insert a new item to the grid.

Auto-filter Popup

In addition to the native CollectionView filtering, the DataGridCollectionView and DataGridDetailDescription classes also support automatic filtering, which provides Excel-like end-user filtering according to the distinct values of each column. Automatic filtering can be enabled by setting the AutoFilterMode property to And or Or (by default, None), indicating whether data items will be filtered according to all or at least one of the filtering criteria defined by each column's auto-filter control. The DistinctValuesConstraint property can also be set to determine if the distinct values are to be filtered according to the result of previous auto-filtering operations.

Statistics Rows and Summary Rows

The StatRow class represents a row that can be used to display statistical results.

Print / Preview

The appearance of a grid when it is printed or exported is determined by the view assigned to a grid's PrintView property and the theme assigned to the view's Theme property. When a grid is printed using the default view and theme, the resulting pages will not have headers or footers and only a column-manager row will be contained in a grid's fixed-header section regardless of the configuration of the runtime grid.

The ShowPrintPreviewWindow and ShowPrintPreviewPopup methods provide print preview capabilities. ShowPrintPreviewPopup should be used when the application is being deployed as an XBAP, as XBAP applications cannot open new windows.

Exporting (CSV, Excel, etc.)

Xceed DataGrid for WPF supports exporting to the XML spreadsheet format (xmlss). These files can be loaded in Excel 2002 and up as well as through the Microsoft Office XP Web Components Spreadsheet Component. The DataGrid also supports exporting to the CSV format, which is compatible with a wide variety of applications.

The DataGridControl class also exposes the ExportToXps method, which allows a grid to be exported as an XPS document.

Column Chooser

The columns that are displayed in a grid can be chosen by the user through the column-chooser context menu, which can be enabled by setting the AllowColumnChooser defined on the view to true. A column's ShowInColumnChooser property determines whether a column's title is displayed in the menu, allowing its visibility to be manipulated by an end user. By default, the column-chooser context menu displays the titles of the columns in the same order as the they are positioned; however, through the ColumnChooserSortOrder property, the order can be changed to sort the titles alphabetically.

Instead of the default context menu style (shown above), the built-in dialog control can be used for a different look/behavior (shown below). A third option is to provide a custom look to the context menu.

Column Splitter Control

When a grid is in a table-view layout, the first n columns can be fixed so that they do not scroll with the grid content. Fixed columns are separated from their scrollable counterparts by a fixed-column splitter, which can be dragged to add or remove fixed columns. Likewise, column-manager cells can be dragged to the left or right of the fixed-column splitter to add or remove fixed columns. The appearance of the fixed-column splitter can be defined for each row type.

Persist User Settings

The settings of a grid and its elements can be persisted and re-applied using the SaveUserSettings and LoadUserSettings methods, respectively. By default, column widths, visibilities, positions, and fixed-column counts as well as grouping and sorting criteria are persisted; merged columns, their positions, and their visibilities can also be persisted. However, these settings can be modified when calling the SaveUserSettings and LoadUserSettings methods.

Merged Column Headers

Merged column headers can be used to present data more clearly and logically. They are displayed in the FixedHeaders section of a grid. Columns can be grouped ("merged") under these merged headers, as can other groups of columns. Merged headers and their columns can be moved (drag-and-drop, programmatically) and removed / added back.

Design-time Support

Xceed DataGrid for WPF provides design-time support for Visual Studio and Expression Blend. In Visual Studio, the DataGridControl control will appear in the toolbox under the Xceed tab and can be added to the design surface by double-clicking on the control or through drag and drop. It's properties can then be modified through the Visual Studio property grid or by using the Xceed DataGrid for WPF Configuration Window.

Excel-like Drag-to-Select Rows and Cells

The datagrid allows users to select multiple items or cells using Left-Click and then dragging the mouse within the datagrid. This allows range selection to be performed without having to hold the Shift key on the keyboard.

To activate this feature, set the DataGrid's AllowDrag property to true, and the DragBehavior property to "Select". The View must be a valid instance or subclass of TableView (ex. TableFlowView, TreeGridflowView).

Asynchronous Binding Mode

The IsAsync property can be used when the get accessor of your binding source property might take a long time. One example is an image property with a get accessor that downloads from the Web. Setting IsAsync to true avoids blocking the UI while the download occurs.

While waiting for the value to arrive, the binding reports the value set on the FallbackValue property, if one is available, or the default value of the binding target property.

Flexible Row

The FlexibleRow class represents a row that can be put inside any header or footer, and can display content that is not bound or related to the grid's data source.

---

↧

New Comment on "ChildWindow"

April 26, 2016, 1:26 am

≫ Next: New Post: IntegerUpDown Minimum and Maximum in Tooltip

≪ Previous: Updated Wiki: Advanced DataGrid

How to allow re-sizing and maximize option on ChildWindow? I can see both happening for ChildWindow in the Live Explorer but its not working while running the example directly from the source.

↧

New Post: IntegerUpDown Minimum and Maximum in Tooltip

April 26, 2016, 3:22 am

≫ Next: New Post: Set maximum value of TimeSpanUpDown

≪ Previous: New Comment on "ChildWindow"

Hi.
I want to show user minimum and maximum value in Tooltip, but it does't work (Tooltip is empty).
I try to bind by ElementName, with FindAncestor - nothing.
If I set binding from external TextBlock - it works.

How I can achieve that?

↧

New Post: Set maximum value of TimeSpanUpDown

April 26, 2016, 3:28 am

≫ Next: New Comment on "ChildWindow"

≪ Previous: New Post: IntegerUpDown Minimum and Maximum in Tooltip

Like this?

<toolkit:TimeSpanUpDown Maximum="23:59:59" />

↧

New Comment on "ChildWindow"

April 26, 2016, 5:26 am

≫ Next: New Post: IntegerUpDown Minimum and Maximum in Tooltip

≪ Previous: New Post: Set maximum value of TimeSpanUpDown

Resizing and maximize options for windows are only available in the Plus version of the Toolkit. The LiveExplorer shows how to use the Plus version of the Toolkit. The source code available on Codeplex is the Community edition. If you want the Plus version, you can buy it here : https://wpftoolkit.codeplex.com/wikipage?title=Compare%20Editions

↧

New Post: IntegerUpDown Minimum and Maximum in Tooltip

April 26, 2016, 1:30 pm

≫ Next: New Post: IntegerUpDown Minimum and Maximum in Tooltip

≪ Previous: New Comment on "ChildWindow"

Hi,

You can use this :

<xctk:IntegerUpDown Margin="5"
                        Minimum="0"
                        Maximum="10"
                        ToolTip="{Binding Maximum, RelativeSource={RelativeSource Self}}" />

And maybe add a Converter to support a binding on Minimum and Maximum values.

↧

New Post: IntegerUpDown Minimum and Maximum in Tooltip

April 27, 2016, 12:30 am

≫ Next: New Post: IntegerUpDown Minimum and Maximum in Tooltip

≪ Previous: New Post: IntegerUpDown Minimum and Maximum in Tooltip

Thank You, this works, but I want to add Minimum and Maximum values to ToolTip. I try to do like this:

<toolkit:IntegerUpDown x:Name="integerUpDown">
  <toolkit:IntegerUpDown.ToolTip>
        <StackPanel>  
           <TextBlock Text="{Binding ElementName=integerUpDown, Path=Minimum, StringFormat=Min: {0}}" />
           <TextBlock Text="{Binding ElementName=integerUpDown, Path=Maximum, StringFormat=Max: {0}}" />
         </StackPanel>  
           </toolkit:IntegerUpDown.ToolTip>
  </toolkit:IntegerUpDown>

Tooltip Shows, but empty. Also I try instead ElementName to do with FindAncestor - without positive.

Any Ideas?

↧

New Post: IntegerUpDown Minimum and Maximum in Tooltip

April 27, 2016, 5:29 am

≫ Next: New Post: IntegerUpDown Minimum and Maximum in Tooltip

≪ Previous: New Post: IntegerUpDown Minimum and Maximum in Tooltip

Try this :

<xctk:IntegerUpDown x:Name="integerUpDown"
                        Margin="5"
                        Minimum="0"
                        Maximum="10">
      <xctk:IntegerUpDown.ToolTip>
        <ToolTip DataContext="{Binding Path=PlacementTarget, RelativeSource={RelativeSource Self}}">
          <StackPanel>
            <TextBlock Text="{Binding Minimum, StringFormat=Min: {0}}" />
            <TextBlock Text="{Binding Maximum, StringFormat=Max: {0}}" />
          </StackPanel>
        </ToolTip>
      </xctk:IntegerUpDown.ToolTip>
</xctk:IntegerUpDown>

↧

New Post: IntegerUpDown Minimum and Maximum in Tooltip

April 27, 2016, 7:28 am

≫ Next: New Post: Disable DataGrid cell focus style

≪ Previous: New Post: IntegerUpDown Minimum and Maximum in Tooltip

This works, thank You! (but it's quite weird;) )

↧

New Post: Disable DataGrid cell focus style

April 29, 2016, 8:42 am

≫ Next: Created Unassigned: MaskedTextBox not binding [22253]

≪ Previous: New Post: IntegerUpDown Minimum and Maximum in Tooltip

Hi,

What version of Windows are you using ?
Which DataGrid are you taking about ? Microsoft DataGrid or Xceed DataGrid from the Toolkit ?1

Thanks.

↧

Created Unassigned: MaskedTextBox not binding [22253]

April 29, 2016, 11:16 am

≫ Next: Updated Wiki: Improvements280

≪ Previous: New Post: Disable DataGrid cell focus style

I'm using Entity Framework and binding the Text property to a datacontext. The binding from the database is not working. If I type data into the textbox and save, the data goes to the database, but the binding back from the database isn't working.

Also, the placeholder for optional characters at the end of the text box are also being saved.

↧

Updated Wiki: Improvements280

May 6, 2016, 5:54 am

≫ Next: Updated Wiki: Improvements280

≪ Previous: Created Unassigned: MaskedTextBox not binding [22253]

v2.7.0 Community Edition (April 6, 2016)

31 bug fixes and improvements

The ZoomBox will no longer throw an exception at startup when its Content is null.
In WatermarkTextBox, the new property KeepWatermarkOnGotFocus makes it possible to keep or remove the watermark on GotFocus.
In PropertyGrid, you can now only display the SelectedObject properties, hidding the inherited ones.
In PropertyGrid, the RefreshPropertiesAttribute is now supported.
In PropertyGrid, Removing the Misc category label is now possible in any language.
In DropDownButton, if KeyboardFocusWithin becomes false, the DropDownButton will now close.
In PropertyGrid, expandable PropertyItems are now updated when their Sub-PropertyItems are modified.
In PropertyGrid, Nullable are now supported.
In DropDownButton, SplitButtons : Under Windows7, Button's Style will now follow Windows 7 and have their bottom half background painted in gray.
In ColorCanvas, the ColorCanvas's SpectrumSlider value will no longer be updated while selecting a color in the ShadingColor rectangle.
In ColorPicker, when the property DisplayColorAndName is False, the Tooltip displaying the Color name will no longer appear in the ColorPicker popup.
In Calculator, the Calculator buttons content won't be overriden with default values anymore. Also, The new property CalculatorButtonPanelTemplate can now be set to define and position the calculator buttons.
In AvalonDock , The BorderBrush, BorderThickness and Background can now be modified when styling a LayoutAnchorableFloatingWindowControl or LayoutDocumentFloatingWindowControl.
In PropertyGrid, Properties Array type, with ExpandableObject attribute, are now displayed in a numerical order instead of alphabetical order to have the indexes displayed correctly.
In AvalonDock, The LayoutDocument and LayoutAnchorable can now be Enabled/Disabled with the new property LayoutContent.IsEnabled.
In MessageBox, the MessageBox owner is now assigned correctly, whether the MessageBox is created normally or from another thread.
In AvalonDock, with a LayoutFloatingWindow active, switching Windows Theme won't cause an invalid Window Handle Exception anymore.
In AvalonDock, the LayoutDocuments repositionning in the LayoutDocumentPane (or the LayoutAnchorable repositionning in the LayoutAnchorablePane) can now be blocked with the new property LayoutPositionableGroup.CanRepositionItems.
In CheckComboBox, CheckComboBox now has the IsEditable property. When True, the TextBox of the CheckComboBox can be edited to specify the SelectedItems.
In CheckComboBox, when using Windows Classic Theme, the CheckMark will no longer disappear when Checked and MouseOver are true.
In DropDownButton and SplitButton, a new property MaxDropDownContent has been created, allowing a maximum height for the popup in the control.
In AvalonDock, using a dark Background Brush for the DockingManager in the System Theme won't hide the icons "DropDownMenu", "Pin" and "Close" anymore.
In NavigationWindow, popping the NavigatorWindow in Windows 8 will no longer throw an exception.
In PropertyGrid, the PrimitiveType Collections will now have their Editor.ItemType set when the collection is inheriting from a List<>.
In AvalonDock, when a LayoutDocument is floating from a LayoutDocumentPane, docking it inside the same LayoutDocumentPane will now set its index to its last position saved instead of 0.
In DateTimePicker, DateTimeUpDown, TimeSpanUpDown, TimePicker and DateTime, Parse is now used inside a try-catch, to prevent crashes for uncommon region settings.
In PropertyGrid, Searching a property will not only be possible with properties "starting" with a set of letters, but also with properties "containing" a set of letters.
In Wizard, with a binding to ItemsSource, it won't be necessary to set the CurrentPage, it will now be automatically set to the first WizardPage.
In RichTextBox, the text selected containing more than 1 color won't disappear anymore.
In MaskedTextBox, the property CharacterCasing is now taken into account when typing letters.
In Chart, when using Axis.LabelsType as "Labels", the values won't be sorted anymore; they will be displayed in the order received.

v2.7.0 Plus Edition

Shipped to registered users of the Plus Edition on June 8, 2015.

New controls

A set of 15 new controls for building apps with the Material Design look, to give your WPF apps a modern look and feel that blends in with the latest Web applications.

A total of 41 bug fixes and improvements

31 bug fixes and improvements from Community Edition 2.7.0
In ToggleSwitch, the properties ThumbLeftContent and ThumbRightContent are now of type "object" instead of "string". So any content can be put in the ToggleSwitch. The property ThumbStyle has been added to redefine the Style of the Thumb. Please note that using ThumbStyle will disable the following properties : ThumbLeftContent, ThumbRightContent, ThumbForeground, ThumbBackground, ThumbBorderBrush, ThumbBorderThickness, ThumbHoverBackground, ThumbHoverBorderBrush, ThumbPressedBackground, ThumbPressedBorderBrush.
In PropertyGrid, using the DependsOn attribute on properties will now update the validation on the depending properties.
In ListBox, the SearchTextBox's Background, BorderThickness and BorderBrush can now be set when styling the ListBox's SearchTextBox.
In ToggleSwitch, the ToggleSwitch can now stretch in all the available space.
In TokenizedTextBox, the event ItemSelectionChanged is now fired when TokenizedTextBox.SelectedItems adds or removes items in code-behind.
In PropertyGrid, EditorNumericUpDownDefinition now supports the property UpdateValueOnEnterKey.
In PropertyGrid, using CustomPropertyItems with customEditors will now have the correct DataContext.
In ListBox, the Drag and Drop will now be available when using a ListBox inside a WinForm's ElementHost.
In ListBox, binding on ListBox.Items.Count now works when ItemsSource is used.
In PropertyGrid, the categories can now be collapsed/expanded in code-behind with 4 new methods :CollapseAllCategories(), ExpandAllCategories(), CollapseCategory(string) and ExpandCategory(string).

v2.8.0 Plus Edition

Shipped to registered users of the Plus Edition on Sept. 14, 2015.

A total of 29 bug fixes and improvements

In ListBox, Grouping a ListBox with an enum type property and selecting an item will now add the selected items in the SelectedItems collection. (Plus Only)
In ListBox, filtering a ListBox with a predicate defined through the ListBox.Filter event will now be considered in the SelectedItems. (Plus Only)
In ListBox, a filtered listbox using grouping will now return the correct SelectedItems by applying the Filter. (Plus Only)
In MaterialListBox, MaterialComboBox and MaterialTabControl, the MaterialControls style is now applied when using ItemsSource. (Plus Only)
In TokenizedTextBox, the TokenizedTextBox's popup will now always be displayed on the same monitor as the TokenizedTextBox. (Plus Only)
In TokenizedTextBox, if the control is placed in a popup, it will now display the tokens correctly. (Plus Only)
In BusyIndicator, the FocusAfterBusy control can now be focused more than once when BusyIndicator is no longer busy.
In AvalonDock, when DockingManager.DocumentsSource changes, the private variable _suspendLayoutItemCreation will now be correctly set during the adding phase.
In AvalonDock, removing a LayoutAnchorable will now null its Content before removing it from his Parent. This prevents memory leaks.
In DropDownButton, Closing the DropDown will no longer throw a null reference exception.
In PropertyGrid, the property AdvancedOptionsMenu is now set in the PropertyGrid's default style, preventing restricted access to propertyGrid in multithreading.
In MaskTextBox, using a null mask will no longer clear the Text value on LostFocus.
In RichTextBoxFormatBar, the correct adorner is now found when there are more than one, preventing a NullReference exception on a drag.
In PropertyGrid, CollectionEditor now takes into account the NewItemTypes attribute.
In DropDownButton, Setting the Focus via the Focus() method won't need a "Tab" to actually focus the DropDownButton.
In AvalonDock, the focus of the active content is now set right away. This prevents the focus issues with comboBoxes in WinForms.
In ZoomBox, The Fit and Fill options of the ZoomBox now centers correctly the ZoomBox content.
In AvalonDock, Clicking the middle mouse button on LayoutDocumentItem header or LayoutAnchorableItem header will no longer throw a Null reference exception.
In NumericUpDown, using a FormatString with "P" can now convert the typed and displayed value as its decimal value. For example, typing 10 will display "10%" and the property "Value" will be "0.1".
In CheckComboBox, changing the CheckComboBox's Foreground now changes the Foreground Color of the ToggleButton it contains.
In AvalonDock, pinning an AutoHideWindow, located in LayoutRoot.XXXSide, now has a correct width. User won't have to extend the ColumnSplitter to see the content. The Width used is the LayoutAnchorable.AutoHideMinWidth.
In CheckComboBox, the control no longer loses its selection while being virtualized.
In DateTimePicker, DateTimeUpDown, years of 2 or 4 digits are now handled. Also, entering a wrong format date will now default to current date, not to 1/1/0001.
In PropertyGrid, the DescriptorPropertyDefinition is no longer ignoring the ConverterCulture in its Binding. This results in correct conversion for text numeric values in PropertyGrid's EditorTemplateDefinition
In AvalonDock, if a floatingWindow is maximized and then the DockingManager is minimized, upon restoring the DockingManager, the floatingWindow will now remain maximized.
In AvalonDock, the new property LayoutDocumentPane.ShowHeader is now available to Show/Hide the TabHeader.
In TimePicker, the method CreateTimeItem is now proptected virtual.
For all toolkit controls, an InvalidOperationException is no longer thrown when VisualTreeHelper gets its child.
For themes different than Windows 8, the exception of type "Initialization of 'Xceed.Wpf.Toolkit.XXX' will no longer be thrown in Visual Studio 2015. This affects all controls of the toolkit.

v2.9.0 Plus Edition

Shipped to registered users of the Plus Edition on February 10, 2016.

A total of 44 improvements and bug fixes

Setting the LicenseKey of a Toolkit Metro Theme in xaml and using a Toolkit control in MainWindow.Resources will no longer result in an exception. (Plus Only)
In the Zoombox, when the property IsUsingScrollBars is true and one of its srollbars is moved, the event Scroll will now be raised. (Plus Only)
In the TokenizedTextBox, the scrollBar’s thumb of the suggestion popup will now have a standard height. (Plus Only)
In the PropertyGrid, when using multi-Selected Objects, the selected objects type and name will now be displayed at top of the PropertyGrid. (Plus Only)
The CollectionControlDialog will now be a StyleableWindow and will be themed when theming is defined in App.xaml. (Plus Only)
In the StyleableWindow, when maximized, the header buttons will no longer be cropped. (Plus Only)
In the ListBox, the Drag and Drop will now work after showing + adding a panel over the Drop area. (Plus Only)
In the ListBox, creating a SelectionRange without a SortDescription’s list and using FromItem/ToItem is now possible. This will result in a selection based on the ListBox dataSource sort, not the ListBox visual sort. (Plus Only)
In the SlideShow, using a binding on ItemsSource will now correctly set the CurrentItem. (Plus Only)
In the TokenizedTextBox, the new event InvalidValueEntered will now be raised when resolving an invalid value. The InvalidValueEventArgs will give access to the invalid value through a Text property. (Plus Only)
The TokenizedTextBox size will now expand normally if there is enough space when adding many items. (Plus Only)
In the ListBox, the addition of a range of items will now be supported resulting in less notifications when many items need to be added.
In the PropertyGrid, selectedObject implementing ICustomTypeDescriptor will now load correctly with a call to customTypeDescriptor.GetPropertyOwner().
In AvalonDock, LayoutAutoHideWindowControl won’t throw an invalid handle exception anymore upon disconnecting-reconnecting from a Virtual Machine.
In Toolkit Metro controls, setting a control’s height will not affect the data displayed in that control.
In AvalonDock, deserialization of custom panes is now supported.
In AvalonDock, the context menu of a LayoutAnchorableFloatingWindowControl will now always show the AnchorableContextMenu.
In the ColorPicker, 2 new events will now be raised when its popup is opened or closed.
In the DateTimePicker, the new property CalendarDisplayMode will now be available to modify the display of the Calendar.
In DateTimePicker, DateTimeUpDown, TimePicker, CalculatorUpDown, FilePicker and TimespanUpDown, the IsTabStop property is now supported.
In DateTimePicker, DateTimeUpDown and TimePicker, the selected date part will now remain selected after the Value property is changed via binding.
In the CollectionControl, a struct type can now be added as a new item.
In AvalonDock, closing the last “Active” LayoutDocument will not set a new “Active” item anymore. This will prevent the AutoHide window popup to be shown as the new default “Active” item.
In the Calculator and CalculatorUpDown, pressing the Memory buttons while an “Error” is displayed in the calculator will not throw a Format exception anymore.
In Calculator and CalculatorUpDown, the MR button can now be used into equations.
In the Magnifier, zooming with the mouseWheel will now be supported.
In the ListBox, adding Value type items is now supported.
In the ListBox, the Equals method override will now be supported for non-primitive type ListBoxItems.
In the Controls using a ButtonSpinner, the “Enter” key will now be disabled when an arrow of the ButtonSpinner has the focus.
In the ListBox, doing a foreach loop on the ListBox.Items property will now be supported.
In the DateTimePicker, only one ValueChanged event will now be raised when selecting a new date.
In the SlideShow, modifying the collection of Items will now correctly set the Previous/Current/Next SlideShow Items.
In AvalonDock, Deserializing a NodeType of type XmlNodeType.Whitespace will no longer throw an exception.
In the CollectionControlDialog, the “Cancel” button will now roll back the changes done in its CollectionControl’s PropertyGrid.
In the PropertyGrid, the interface ICustomTypeProvider is now supported for the SelectedObject.
In the PropertyGrid, the Resources properties will now display the correct icon when ShowAdvancedOptions is True.
In DateTimePicker, CalculatorUpDown, ColorPicker, DropDownButton, MultiLineTextEditor and TimePicker, the Tooltip will now be used only in the collapsed part of the control; the popup will no longer display it.
In the PropertyGrid, the editor for properties of type FontFamily will now be a comboBox containing sorted Font names.
In the DateTimeUpDown, TimeSpanUpDown, TimePicker and DateTimePicker, the new property CurrentDateTimePart is now available to set the date time part that can be changed with the Up/Down buttons or the Up/Down keys.
In the DateTimeUpDown, TimeSpanUpDown, DateTimePicker and TimePicker, the new property “Step” can now be set to customize the increment/decrement value of DateTime controls.
In the PropertyGrid, the new event IsPropertyBrowsable will now be raised at the creation of each PropertyItem in order to use the callback and individually set the visibility of each propertyItem in the PropertyGrid.
In the NumericUpDowns, DateTimeUpDown, DateTimePicker, TimePicker and TimeSpanUpDown, the new event Spinned will now be raised when an Increment/Decrement action is initiated.
The Metro theme Toolkit controls will now share the same height as the core metro theme controls.

v3.0.0 Plus Edition

Shipped to registered users of the Plus Edition on April 5, 2016.

New controls

MultiCalendar control. Lets you present and allow date selections on multiple calendars positioned in any number of rows and columns. (Plus Only)
WatermarkPasswordBox control. Lets users enter a password that gets stored in a SecureString, and displays a watermark if no password is defined.

A total of 43 improvements and bug fixes

In the TokenizedTextBox, setting the focus will now be supported in code-behind. (Plus Only)
In the Calendar, when using the Metro theme, the “X” for the Blackout dates will now be visible. (Plus Only)
In the MaterialTextField, updating the Text property with a binding will now animate the Watermark accordingly. (Plus Only)
In the Chart, the new property IntersectMinValue will make it possible to move an axis on the other side of the chart. (Plus Only)
In the Chart, changing the collection of DataPoints will now update the axis so that the layout will fill the chart dimension. (Plus Only)
In the ListBox, the SelectedItems.Count will now be correctly updated when the ListBox is not visible. (Plus Only)
In the ListBox, the ItemsCount will now be updated when the ListBox is filtered. (Plus Only)
In the Chart, using a series.DataPointsSource binding will now refresh the series when the binding source is updated. (Plus Only)
In the ListBox, setting a Filtercontrol.DataSourceFilterExpression in code-behind will now update (if possible) the SearchTextBox with the provided filter. (Plus Only)
In the ListBox, clearing the ListBox’s source right after a FilterControl’s filter is set to null (without a layout pass between the 2 actions) will no longer throw a NullRefException. (Plus Only)
In the ListBox, the scrollbars won’t be displayed anymore when using a filter and adding new items when there is enough space to display all those items. (Plus Only)
In the TokenizedTextBox, the property IsValid will no longer have a setter. (Plus Only)
In the StyleableWindow, a new property TitleFontSize can now be used to set. (Plus Only)
In the NumericUpDown, DateTimeUpDown, DateTimePicker, TimePicker, TimeSpanUpDown and CalulatorUpDown, when the property UpdateValueOnEnterKey is True, the ButtonSpinners, the keyboard arrows and the mouse wheel will no longer update the Value property. The Value property will now only be updated on a “Enter” key press or a lost focus of the UpDown control.
In the CollectionControl, objects of type ICollection and IList are now be supported.
In the UpDown controls, when the Value property is bound to a property which coerce the received value, the Text property will now be refreshed accordingly.
In the TimeSpanUpDown, selecting the minus sign(“-“) with the mouse and incrementing/decrementing the control will no longer reset the Value to null.
In the ListBox, doing a ListBoxItem drag while its drop fade out animation isn’t completed will no longer result in a Null reference exception.
In the CollectionControl, the objects of type IDictionary are now supported.
In the NumericUpDowns, when the property ClipValueToMinMax is True and the property Minimum becomes greater than Value (or the property Maximum becomes lower than Value), the Value property will now be re-evaluated to respect the Minimum – Maximum range.
In the SplitButton, the BorderThickness will now be modifiable.
In the PropertyGrid, when trying to edit a List of T, the CollectionControlDialog will no longer crash if the T class doesn’t include a default Constructor.
In the PropertyGrid, registering to the IsPropertyBrowsable event and not doing anything in the callback, will no longer display the properties with BrowsableAttribute(false).
In the CollectionControl, the ListBoxItem will now be updated when a property value is modified in the PropertyGrid.
In the PropertyGrid, the DisplayAttribute will now be supported for PropertyItems.
In the Wizard, the Finish event will now be a CancelRoutedEventHandler.
In NumericUpDowns, the FormatString property will now accept strings like the BindingBase.StringFormat. Ex : “{}{0:N2} ms”.
In the CheckListBox, the selectedItems will not be cleared anymore if the ItemSource’s filter is removed.
The PropertyGrid will now support the Range attribute to set the Maximum/Minimum properties on NumericUpDown/DateTimeUpDown and TimeSpanUpDown editors.
In AvalonDock, DockingManager.LogicalChildren will now be correctly updated when a LayoutDocument/LayoutAnchorable is removed by modifying the DockingManager.DocumentsSource/AnchorablesSource properties or by closing a LayoutDocument/LayoutAnchorable.
In the PropertyGrid, the attribute TypeConverter (of type ExpandableObjectConverter) will now be supported to expand a PropertyItem.
In the PropertyGrid, TypeConverter.GetStandardValues() will now be supported to display options in a ComboBox editor.
In the NumericUpDowns, DatetimePicker, SplitButton, RichTextBoxFormatBar, MultiLineTextEditor, DropDownButton, ColorPicker, CollectionControl, CalculatorUpDown, and TimePicker, the arrows will not look pixelated anymore in high DPI.
In the PropertyGrid, the setter of an expandable propertyItem will now be called when one of its sub-propertyItem is modified.
In the DateTime controls, using a Custom format with no dateTime separators will now correctly display the selected dateTime.
In the DropDownButton and the SplitButton, the new property DropDownPosition will now be available to set the position of the popup relative to the control.
In the RangeSlider, setting a LowerValue greater than HigherValue will no longer be possible. Setting a HigherValue smaller than LowerValue is also no longer possible.
In the TimeSpanUpDown, only numeric characters will now be accepted.
In the WatermarkComboBox, the toggleButton will now use the DisplayMemberPath when specified.
In the Modal ChildWindow and the MessageBox, Tab navigation will now remain inside the control. Also, the Menu shortcut keys will no longer be available.
In the ColorPicker, pressing the “Esc” Key will now reset the SelectedColor to the last selected color.

We hope you love this release and decide to support the project.
-- Xceed Team

↧

Updated Wiki: Improvements280

May 6, 2016, 5:58 am

≫ Next: Updated Wiki: Home

≪ Previous: Updated Wiki: Improvements280

v2.8.0 Community Edition (May 6, 2016)

23 bug fixes and improvements

In BusyIndicator, the FocusAfterBusy control can now be focused more than once when BusyIndicator is no longer busy.
In AvalonDock, when DockingManager.DocumentsSource changes, the private variable _suspendLayoutItemCreation will now be correctly set during the adding phase.
In AvalonDock, removing a LayoutAnchorable will now null its Content before removing it from his Parent. This prevents memory leaks.
In DropDownButton, Closing the DropDown will no longer throw a null reference exception.
In PropertyGrid, the property AdvancedOptionsMenu is now set in the PropertyGrid's default style, preventing restricted access to propertyGrid in multithreading.
In MaskTextBox, using a null mask will no longer clear the Text value on LostFocus.
In RichTextBoxFormatBar, the correct adorner is now found when there are more than one, preventing a NullReference exception on a drag.
In PropertyGrid, CollectionEditor now takes into account the NewItemTypes attribute.
In DropDownButton, Setting the Focus via the Focus() method won't need a "Tab" to actually focus the DropDownButton.
In AvalonDock, the focus of the active content is now set right away. This prevents the focus issues with comboBoxes in WinForms.
In ZoomBox, The Fit and Fill options of the ZoomBox now centers correctly the ZoomBox content.
In AvalonDock, Clicking the middle mouse button on LayoutDocumentItem header or LayoutAnchorableItem header will no longer throw a Null reference exception.
In NumericUpDown, using a FormatString with "P" can now convert the typed and displayed value as its decimal value. For example, typing 10 will display "10%" and the property "Value" will be "0.1".
In CheckComboBox, changing the CheckComboBox's Foreground now changes the Foreground Color of the ToggleButton it contains.
In AvalonDock, pinning an AutoHideWindow, located in LayoutRoot.XXXSide, now has a correct width. User won't have to extend the ColumnSplitter to see the content. The Width used is the LayoutAnchorable.AutoHideMinWidth.
In CheckComboBox, the control no longer loses its selection while being virtualized.
In DateTimePicker, DateTimeUpDown, years of 2 or 4 digits are now handled. Also, entering a wrong format date will now default to current date, not to 1/1/0001.
In PropertyGrid, the DescriptorPropertyDefinition is no longer ignoring the ConverterCulture in its Binding. This results in correct conversion for text numeric values in PropertyGrid's EditorTemplateDefinition
In AvalonDock, if a floatingWindow is maximized and then the DockingManager is minimized, upon restoring the DockingManager, the floatingWindow will now remain maximized.
In AvalonDock, the new property LayoutDocumentPane.ShowHeader is now available to Show/Hide the TabHeader.
In TimePicker, the method CreateTimeItem is now proptected virtual.
For all toolkit controls, an InvalidOperationException is no longer thrown when VisualTreeHelper gets its child.
For themes different than Windows 8, the exception of type "Initialization of 'Xceed.Wpf.Toolkit.XXX' will no longer be thrown in Visual Studio 2015. This affects all controls of the toolkit.

v2.8.0 Plus Edition

Shipped to registered users of the Plus Edition on Sept. 14, 2015.

A total of 29 bug fixes and improvements

23 bug fixes and improvements from the Community Edition listed above, plus 6 more listed here.
In ListBox, Grouping a ListBox with an enum type property and selecting an item will now add the selected items in the SelectedItems collection.
In ListBox, filtering a ListBox with a predicate defined through the ListBox.Filter event will now be considered in the SelectedItems.
In ListBox, a filtered listbox using grouping will now return the correct SelectedItems by applying the Filter.
In MaterialListBox, MaterialComboBox and MaterialTabControl, the MaterialControls style is now applied when using ItemsSource.
In TokenizedTextBox, the TokenizedTextBox's popup will now always be displayed on the same monitor as the TokenizedTextBox.
In TokenizedTextBox, if the control is placed in a popup, it will now display the tokens correctly.

v2.9.0 Plus Edition

Shipped to registered users of the Plus Edition on February 10, 2016.

A total of 44 improvements and bug fixes

Setting the LicenseKey of a Toolkit Metro Theme in xaml and using a Toolkit control in MainWindow.Resources will no longer result in an exception. (Plus Only)
In the Zoombox, when the property IsUsingScrollBars is true and one of its srollbars is moved, the event Scroll will now be raised. (Plus Only)
In the TokenizedTextBox, the scrollBar’s thumb of the suggestion popup will now have a standard height. (Plus Only)
In the PropertyGrid, when using multi-Selected Objects, the selected objects type and name will now be displayed at top of the PropertyGrid. (Plus Only)
The CollectionControlDialog will now be a StyleableWindow and will be themed when theming is defined in App.xaml. (Plus Only)
In the StyleableWindow, when maximized, the header buttons will no longer be cropped. (Plus Only)
In the ListBox, the Drag and Drop will now work after showing + adding a panel over the Drop area. (Plus Only)
In the ListBox, creating a SelectionRange without a SortDescription’s list and using FromItem/ToItem is now possible. This will result in a selection based on the ListBox dataSource sort, not the ListBox visual sort. (Plus Only)
In the SlideShow, using a binding on ItemsSource will now correctly set the CurrentItem. (Plus Only)
In the TokenizedTextBox, the new event InvalidValueEntered will now be raised when resolving an invalid value. The InvalidValueEventArgs will give access to the invalid value through a Text property. (Plus Only)
The TokenizedTextBox size will now expand normally if there is enough space when adding many items. (Plus Only)
In the ListBox, the addition of a range of items will now be supported resulting in less notifications when many items need to be added.
In the PropertyGrid, selectedObject implementing ICustomTypeDescriptor will now load correctly with a call to customTypeDescriptor.GetPropertyOwner().
In AvalonDock, LayoutAutoHideWindowControl won’t throw an invalid handle exception anymore upon disconnecting-reconnecting from a Virtual Machine.
In Toolkit Metro controls, setting a control’s height will not affect the data displayed in that control.
In AvalonDock, deserialization of custom panes is now supported.
In AvalonDock, the context menu of a LayoutAnchorableFloatingWindowControl will now always show the AnchorableContextMenu.
In the ColorPicker, 2 new events will now be raised when its popup is opened or closed.
In the DateTimePicker, the new property CalendarDisplayMode will now be available to modify the display of the Calendar.
In DateTimePicker, DateTimeUpDown, TimePicker, CalculatorUpDown, FilePicker and TimespanUpDown, the IsTabStop property is now supported.
In DateTimePicker, DateTimeUpDown and TimePicker, the selected date part will now remain selected after the Value property is changed via binding.
In the CollectionControl, a struct type can now be added as a new item.
In AvalonDock, closing the last “Active” LayoutDocument will not set a new “Active” item anymore. This will prevent the AutoHide window popup to be shown as the new default “Active” item.
In the Calculator and CalculatorUpDown, pressing the Memory buttons while an “Error” is displayed in the calculator will not throw a Format exception anymore.
In Calculator and CalculatorUpDown, the MR button can now be used into equations.
In the Magnifier, zooming with the mouseWheel will now be supported.
In the ListBox, adding Value type items is now supported.
In the ListBox, the Equals method override will now be supported for non-primitive type ListBoxItems.
In the Controls using a ButtonSpinner, the “Enter” key will now be disabled when an arrow of the ButtonSpinner has the focus.
In the ListBox, doing a foreach loop on the ListBox.Items property will now be supported.
In the DateTimePicker, only one ValueChanged event will now be raised when selecting a new date.
In the SlideShow, modifying the collection of Items will now correctly set the Previous/Current/Next SlideShow Items.
In AvalonDock, Deserializing a NodeType of type XmlNodeType.Whitespace will no longer throw an exception.
In the CollectionControlDialog, the “Cancel” button will now roll back the changes done in its CollectionControl’s PropertyGrid.
In the PropertyGrid, the interface ICustomTypeProvider is now supported for the SelectedObject.
In the PropertyGrid, the Resources properties will now display the correct icon when ShowAdvancedOptions is True.
In DateTimePicker, CalculatorUpDown, ColorPicker, DropDownButton, MultiLineTextEditor and TimePicker, the Tooltip will now be used only in the collapsed part of the control; the popup will no longer display it.
In the PropertyGrid, the editor for properties of type FontFamily will now be a comboBox containing sorted Font names.
In the DateTimeUpDown, TimeSpanUpDown, TimePicker and DateTimePicker, the new property CurrentDateTimePart is now available to set the date time part that can be changed with the Up/Down buttons or the Up/Down keys.
In the DateTimeUpDown, TimeSpanUpDown, DateTimePicker and TimePicker, the new property “Step” can now be set to customize the increment/decrement value of DateTime controls.
In the PropertyGrid, the new event IsPropertyBrowsable will now be raised at the creation of each PropertyItem in order to use the callback and individually set the visibility of each propertyItem in the PropertyGrid.
In the NumericUpDowns, DateTimeUpDown, DateTimePicker, TimePicker and TimeSpanUpDown, the new event Spinned will now be raised when an Increment/Decrement action is initiated.
The Metro theme Toolkit controls will now share the same height as the core metro theme controls.

v3.0.0 Plus Edition

Shipped to registered users of the Plus Edition on April 5, 2016.

New controls

MultiCalendar control. Lets you present and allow date selections on multiple calendars positioned in any number of rows and columns. (Plus Only)
WatermarkPasswordBox control. Lets users enter a password that gets stored in a SecureString, and displays a watermark if no password is defined.

A total of 43 improvements and bug fixes

In the TokenizedTextBox, setting the focus will now be supported in code-behind. (Plus Only)
In the Calendar, when using the Metro theme, the “X” for the Blackout dates will now be visible. (Plus Only)
In the MaterialTextField, updating the Text property with a binding will now animate the Watermark accordingly. (Plus Only)
In the Chart, the new property IntersectMinValue will make it possible to move an axis on the other side of the chart. (Plus Only)
In the Chart, changing the collection of DataPoints will now update the axis so that the layout will fill the chart dimension. (Plus Only)
In the ListBox, the SelectedItems.Count will now be correctly updated when the ListBox is not visible. (Plus Only)
In the ListBox, the ItemsCount will now be updated when the ListBox is filtered. (Plus Only)
In the Chart, using a series.DataPointsSource binding will now refresh the series when the binding source is updated. (Plus Only)
In the ListBox, setting a Filtercontrol.DataSourceFilterExpression in code-behind will now update (if possible) the SearchTextBox with the provided filter. (Plus Only)
In the ListBox, clearing the ListBox’s source right after a FilterControl’s filter is set to null (without a layout pass between the 2 actions) will no longer throw a NullRefException. (Plus Only)
In the ListBox, the scrollbars won’t be displayed anymore when using a filter and adding new items when there is enough space to display all those items. (Plus Only)
In the TokenizedTextBox, the property IsValid will no longer have a setter. (Plus Only)
In the StyleableWindow, a new property TitleFontSize can now be used to set. (Plus Only)
In the NumericUpDown, DateTimeUpDown, DateTimePicker, TimePicker, TimeSpanUpDown and CalulatorUpDown, when the property UpdateValueOnEnterKey is True, the ButtonSpinners, the keyboard arrows and the mouse wheel will no longer update the Value property. The Value property will now only be updated on a “Enter” key press or a lost focus of the UpDown control.
In the CollectionControl, objects of type ICollection and IList are now be supported.
In the UpDown controls, when the Value property is bound to a property which coerce the received value, the Text property will now be refreshed accordingly.
In the TimeSpanUpDown, selecting the minus sign(“-“) with the mouse and incrementing/decrementing the control will no longer reset the Value to null.
In the ListBox, doing a ListBoxItem drag while its drop fade out animation isn’t completed will no longer result in a Null reference exception.
In the CollectionControl, the objects of type IDictionary are now supported.
In the NumericUpDowns, when the property ClipValueToMinMax is True and the property Minimum becomes greater than Value (or the property Maximum becomes lower than Value), the Value property will now be re-evaluated to respect the Minimum – Maximum range.
In the SplitButton, the BorderThickness will now be modifiable.
In the PropertyGrid, when trying to edit a List of T, the CollectionControlDialog will no longer crash if the T class doesn’t include a default Constructor.
In the PropertyGrid, registering to the IsPropertyBrowsable event and not doing anything in the callback, will no longer display the properties with BrowsableAttribute(false).
In the CollectionControl, the ListBoxItem will now be updated when a property value is modified in the PropertyGrid.
In the PropertyGrid, the DisplayAttribute will now be supported for PropertyItems.
In the Wizard, the Finish event will now be a CancelRoutedEventHandler.
In NumericUpDowns, the FormatString property will now accept strings like the BindingBase.StringFormat. Ex : “{}{0:N2} ms”.
In the CheckListBox, the selectedItems will not be cleared anymore if the ItemSource’s filter is removed.
The PropertyGrid will now support the Range attribute to set the Maximum/Minimum properties on NumericUpDown/DateTimeUpDown and TimeSpanUpDown editors.
In AvalonDock, DockingManager.LogicalChildren will now be correctly updated when a LayoutDocument/LayoutAnchorable is removed by modifying the DockingManager.DocumentsSource/AnchorablesSource properties or by closing a LayoutDocument/LayoutAnchorable.
In the PropertyGrid, the attribute TypeConverter (of type ExpandableObjectConverter) will now be supported to expand a PropertyItem.
In the PropertyGrid, TypeConverter.GetStandardValues() will now be supported to display options in a ComboBox editor.
In the NumericUpDowns, DatetimePicker, SplitButton, RichTextBoxFormatBar, MultiLineTextEditor, DropDownButton, ColorPicker, CollectionControl, CalculatorUpDown, and TimePicker, the arrows will not look pixelated anymore in high DPI.
In the PropertyGrid, the setter of an expandable propertyItem will now be called when one of its sub-propertyItem is modified.
In the DateTime controls, using a Custom format with no dateTime separators will now correctly display the selected dateTime.
In the DropDownButton and the SplitButton, the new property DropDownPosition will now be available to set the position of the popup relative to the control.
In the RangeSlider, setting a LowerValue greater than HigherValue will no longer be possible. Setting a HigherValue smaller than LowerValue is also no longer possible.
In the TimeSpanUpDown, only numeric characters will now be accepted.
In the WatermarkComboBox, the toggleButton will now use the DisplayMemberPath when specified.
In the Modal ChildWindow and the MessageBox, Tab navigation will now remain inside the control. Also, the Menu shortcut keys will no longer be available.
In the ColorPicker, pressing the “Esc” Key will now reset the SelectedColor to the last selected color.

We hope you love this release and decide to support the project.
-- Xceed Team

↧