Breaking Changes in v2010 vol 2.4
This page lists important behavior and API changes, which were introduced in this version. If you already have projects using DXperience, you will need to peruse this list in order to understand the changes you might need to make to your source code to support this new release. Note that we only publish the changes to the public interface of our controls. We reserve the right to change the protected, internal, or private interfaces when needed.
Table of Contents
All .NET WinForms Components
BC1053: The Asphalt Word skin has been moved to the DevExpress.BonusSkins library. To use this skin, the BonusSkins library must be added and registered in your project. To use The Asphalt World skin, ensure that the DevExpress.BonusSkins library is added to the References section of your project.
You also need to register the library for runtime use, as described in the How to: Use a Skin from an External Skin Library help topic:
[C#]
[STAThread]
static void Main() {
DevExpress.UserSkins.BonusSkins.Register();
Application.Run(new Form1());
}
BC1054: The position of The Asphalt World skin caption in the BarStringID.SkinCaptions string has been changed The string identified by the BarString.SkinCaptions ID contains the names of all DevExpress skins.
It's used to populate a menu or Ribbon gallery with DevExpress skin items (see How to populate a menu and Ribbon gallery with DevExpress skin items and localize them to learn more).
You can localize this string to change the skin display names. The Asphalt World skin has been moved to the DevExpress.BonusSkins library. The position of the "The Asphalt World" sub-string in the BarString.SkinCaptions string has also been changed. The old zero-based position of this skin caption is 3. The new zero-based position is 35. You need to change your custom localized string accordingly, if required. The position 3 in the BarString.SkinCaptions string is now occupied by the caption of the new DevExpress Dark Style skin, as this skin is included into the DevExpress.Utils library.
ASPxPivotGrid
BC1048: New items added to PivotCustomFilterPopupItemsEventArgs.Items collection should provide values of data column type The PivotGridFilterItem.Value property of the newly added PivotCustomFilterPopupItemsEventArgs.Items collection item in the PivotCustomFilterPopupItems event handler should contain a value that is convertible to the column data type (PivotCustomFilterPopupItemsEventArgs.Field.DataType).
DXCharts for WPF
BC1047: Some types have become obsolete. The following classes are now obsolete: - Bar2DSection;
- Candle2DSection;
- ChartVisualElement;
- CollectionOfTExtensionBase;
- CustomBar2DSection;
- CustomCandle2DSection;
- CustomStick2DSection;
- CustomStock2DSection;
- Financial2DSection;
- ObservableCollectionExtension;
- PredefinedBar2DSection;
- PredefinedCandle2DSection;
- PredefinedStick2DSection
- PredefinedCandle2DSection
- Stock2DSection
- PredefinedStock2DSection The following enumerations are now obsolete: - Bar2DDrawingOrder;
- Bar2DStackedDrawingOrder BC1039: The PredefinedBar2DModel constructor has become obsolete. BC1040: The SymmetricBar2DModel constructor has become obsolete.
DXPivotGrid for WPF
BC1050: Some XAML styles have been changed. - The FieldHeaderThemeKey.ButtonContentTemplate style's TargetType property has been changed from ContentControl to FieldHeaderContentControl. - The FieldHeaderThemeKey.ButtonStyle style's DataContext property has been changed from PivotGridField to FieldHeader. - Styles for FieldDataCellContentPresenter and FieldDataValueContentPresenter have been replaced with a style for PivotContentPresenter.
DXRichEdit for Silverlight
BC1043: GetPositionFromPoint takes its argument in coordinates relative to a control. DevExpress.Xpf.RichEdit.RichEditControl.GetPositionFromPoint takes an argument in coordinates relative to RichEditControl, and not in coordinates relative to its parent as it was before. The correct use of the GetPositionFromPoint method is shown below: Point point = e.GetPosition((UIElement)richEdit1.RichControl);
System.Drawing.Point pt = Units.PixelsToDocuments(new System.Drawing.Point((int)point.X,
(int)point.Y), richEdit1.RichControl.DpiX, richEdit1.RichControl.DpiY);
DocumentPosition pos = richEdit1.RichControl.GetPositionFromPoint(pt);
PivotGrid Core
BC1044: Starting from 2010 vol 2.4, PivotGrid will not evaluate field expressions if there is no datasource specified. BC1049: The PivotGridFieldOptions.OLAPFilterUsingWhereClause property type has been changed to the PivotOLAPFilterUsingWhereClause enumeration. Previously, the PivotGridFieldOptions.OLAPFilterUsingWhereClause property was Boolean: public bool OLAPFilterUsingWhereClause Starting from v2010 vol.4, the PivotGridFieldOptions.OLAPFilterUsingWhereClause property holds the PivotOLAPFilterUsingWhereClause enumeration members: public PivotOLAPFilterUsingWhereClause OLAPFilterUsingWhereClause
public enum PivotOLAPFilterUsingWhereClause {
SingleValuesOnly,
Always,
Never
}
The PivotOLAPFilterUsingWhereClause enumeration members are described below: - PivotOLAPFilterUsingWhereClause.Always - the WHERE clause is always used (equals true); - PivotOLAPFilterUsingWhereClause.Never - the WHERE clause is never used (equals false); - PivotOLAPFilterUsingWhereClause.SingleValuesOnly - the WHERE clause is used when filter condition contains a single field value included in the pivot grid (in OLAP mode). Otherwise, a sub-select clause is used. Default value: PivotOLAPFilterUsingWhereClause.SingleValuesOnly
XtraReports Suite
BC1042: The AutoShowParametersPanel property default value has been changed to true. Now, the Parameters panel is shown in the Print Preview by default, if there are visible parameters in the report.
|