If this option is disabled, these columns/bands/fields will be added to the current control. Specifies whether or not columns/bands/fields that exist in the layout being loaded, but not in the current control’s layout, should be discarded.
If this option is disabled, these columns/bands/fields will be discarded. Specifies whether or not columns/bands/fields that exist in the current control’s layout, but not in the layout being loaded, should be retained. These options include view settings, data binding, behavior options, end-user customization options, and selection settings. Grouping, sorting, filtering and summary settings.Īll options except for appearance settings and style conditions. View options - ColumnView.OptionsView and PivotGridControl.OptionsView for Grid Control and XtraPivotGrid respectively. The options provided by the OptionsLayout object are listed below. To manually specify which options need to be saved/restored, use the control’s OptionsLayout property ( BaseView.OptionsLayout for Grid Control Views and PivotGridControl.OptionsLayout for XtraPivotGrid). Options such as appearance, data binding, behavior, customization and selection are not saved/restored by default. all settings grouped within the control’s OptionsView object (for instance, ColumnView.OptionsView).current and most recently used (MRU) filters.visibility state, position and size of the columns/bands/fields.When calling the SaveLayoutTo… or RestoreLayoutFrom… method without the options parameter, only a subset of the control’s settings is saved/restored. Public void RestoreLayoutFromXml(string xmlFile, OptionsLayoutBase options) Public void RestoreLayoutFromXml(string xmlFile) Public void SaveLayoutToXml(string xmlFile, OptionsLayoutBase options)
Public void SaveLayoutToXml(string xmlFile) For instance, the overloads of the BaseView.SaveLayoutToXml and BaseView.RestoreLayoutFromXml methods are declared as follows.
The SaveLayoutTo… and RestoreLayoutFrom… methods have two overloads (with and without the options parameter of the OptionsLayoutBase type). The complete list of methods can be found in the following topics. For instance, the BaseView.SaveLayoutToXml and BaseView.RestoreLayoutFromXml methods can be used to save/restore a Grid Control’s View using an XML file. All these methods start with either SaveLayoutTo… or RestoreLayoutFrom…. Grid Control and PivotGrid controls provide methods to save control layout to and then restore it from a data store (an XML file, a stream or the system registry). This document describes methods that implement this functionality. The Xtra Grid is not just a grid, it is a high performance data shaping, data mining and reporting platform, so you can unleash the power of information and intuitively present it to your end-users.Grid Control and XtraPivotGrid allow you to control how their layouts are stored to and restored from data stores. The Xtra Grid delivers powerful runtime experiences including Column, Row and Preview Customizations. Easy-to-use features are built-in to the Xtra Grid so you can deliver solutions that can be customized at both design and runtime as needs dictate. It also shapes, organizes and informs with sort, group, compute - print and export options. It gives you a comprehensive set of UI choices so you can deliver solutions that solve real-world business problems. The Xtra Grid includes 7 elegant Grid View options and is incredibly efficient at displaying information and allowing your users to manipulate data on-screen. And with asynchronous data loading mode, your app will always remain responsive regardless of data set size or complexity. Whether using it in bound, unbound or master-detail mode, you can enable many of its features including a built-in printing engine for instant ad-hoc reporting, without writing a single line of code. XtraGrid (Xtra Grid) includes patent-pending server side data processing and is a feature-complete editing and data shaping component allowing your end-users to easily manage information and display it on-screen.