Log In
[Expand]General Information
[Collapse]WinForms Controls
 [Expand]What's Installed
 [Expand]Build an Application
 [Collapse]Controls and Libraries
  [Expand]Forms and User Controls
  [Expand]Messages, Notifications and Dialogs
  [Expand]Editors and Simple Controls
  [Expand]Ribbon, Bars and Menu
  [Expand]Application UI Manager
  [Expand]Docking Library
  [Collapse]Data Grid
   [Expand]Getting Started
   [Expand]Binding to Data
   [Expand]Grid View
   [Collapse]View Technology
    [Expand]Banded Grid Views
    [Expand]Card View
    [Expand]Layout View
    [Expand]Tile View
    [Expand]WinExplorer View
     View Hierarchy
   [Expand]Data Editing
   [Expand]Filtering and Locating Rows
   [Expand]Focus and Selection Handling
   [Expand]Processing Rows
   [Expand]Formatting Cell Values
   [Expand]Master-Detail Relationships
   [Expand]Asynchronous Image Load
   [Expand]Export and Printing
   [Expand]Appearance and Conditional Formatting
   [Expand]Batch Modifications
   [Expand]Hit Information
   [Expand]Popup Menus
   [Expand]Saving and Restoring Layouts
   [Expand]Visual Elements
   [Expand]Design-Time Features
   [Expand]End-User Capabilities
    Included Components
  [Expand]Vertical Grid
  [Expand]Pivot Grid
  [Expand]Tree List
  [Expand]Chart Control
  [Expand]Map Control
  [Expand]Rich Text Editor
  [Expand]Spell Checker
  [Expand]Form Layout Managers
  [Expand]Navigation Controls
  [Expand]PDF Viewer
  [Expand]TreeMap Control
 [Expand]Common Features
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Document Server
[Expand]Report Server
[Expand]eXpressApp Framework
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

View Hierarchy

Grid Control uses views to display data from a bound data source. This document describes the hierarchy of View classes provided by XtraGrid.

  • BaseView is the root View class that implements the basic functionality. Since the class is abstract, you cannot create instances. This class declares virtual methods to work with editors, appearances, hints, details and saving and restoring layouts, but these are implemented by class descendants.

  • ColumnView introduces methods to work with columns and rows/records (see Rows and Cards Overview). This class is also abstract, so you cannot create instances.

    Columns represent fields from a bound data source, while rows correspond to data source records. ColumnView does not determine how columns and rows are arranged. The ColumnView class implements methods to manipulate columns, access specific rows and cells, maximize details, display hints, sort and filter data, and select multiple rows.

  • GridView represents data in a tabular form.

    This View supports grouping, incremental search, summary calculation, master-detail relationship display and preview section display. It also provides a means to customize a View layout via context menus. Columns can be anchored to the left or to the right of the View edge. Such columns are not horizontally scrolled within a View. See the Grid View document to learn more.

  • BandedGridView extends the functionality of the Grid View by introducing bands used to combine similar columns. Columns can only be displayed by adding them to bands. Hiding a band automatically hides all columns that belong to that band. The BandedGridView class only supports a single-line column arrangement. Bands can be anchored to the left or right edge. Fixed columns are not supported. See the Banded Grid View document to learn more.

  • AdvBandedGridView extends the functionality of the BandedGridView. The View allows you to arrange columns within bands into multiple lines. Columns can have different heights. See the Advanced Banded Grid View document to learn more.

  • LayoutView displays records as cards that support multiple field layouts. Cards can be arranged in single or multiple columns or rows, or in an advanced carousel mode in which cards form an ellipse with a transparency effect. See the Layout View topic to learn more.

  • CardView displays each record as a simple card, arranging fields vertically in a single column. See the Card View document to learn more.

  • WinExplorerView implements the Windows Explorer UI to display your data in one of seven available Styles. Refer to the WinExplorer View topic for details.

  • TileView is an evolution of the CardView that displays grid data as Windows 10-styled tiles. See the Tile View document for more info.
If these Views do not meet your particular needs, you can create a custom View class by deriving from the one that most closely matches your requirements. If you need to implement a completely new data representation, you can derive from the BaseView class. The ColumnView class provides methods to work with columns. So, you can derive from this class if you need to arrange columns in a particular manner. If you only need to modify the default behavior of GridView, BandedGridView, AdvBandedGridView or CardView, then you should inherit from the corresponding class.

Information on the View element layout is stored in the View's protected ViewInfo object. This specifies the position and size of its elements. Each View also provides a Painter object, which paints the View based on the current look and feel. The Painter object renders the View using information from ViewInfo and the View's settings. Handler is another significant View object. It handles keyboard and mouse events initiated by an end-user.

Expanded See Also

How would you rate this topic?​​​​​​​