Log In
Home
Support
Demos
Documentation
Blogs
Training
Webinars
[Expand]General Information
[Collapse]WinForms Controls
  Prerequisites
 [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
   [Expand]View Technology
   [Expand]Grouping
   [Expand]Sorting
   [Expand]Summaries
   [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
   [Collapse]Appearance and Conditional Formatting
    [Collapse]Look and Feel
      Look And Feel Overview
      Skins
      Look and Feel Inheritance
    [Expand]Appearances
    [Expand]Conditional Formats
    [Expand]Custom Painting
    [Expand]Alpha Blending and Background Images
   [Expand]Batch Modifications
   [Expand]Hit Information
   [Expand]Hints
   [Expand]Popup Menus
   [Expand]Saving and Restoring Layouts
   [Expand]Visual Elements
   [Expand]Design-Time Features
   [Expand]Examples
   [Expand]End-User Capabilities
    Included Components
  [Expand]Vertical Grid
  [Expand]Pivot Grid
  [Expand]Tree List
  [Expand]Chart Control
  [Expand]Diagrams
  [Expand]Gauges
  [Expand]Map Control
  [Expand]Scheduler
  [Expand]Spreadsheet
  [Expand]Rich Text Editor
  [Expand]Spell Checker
  [Expand]Form Layout Managers
  [Expand]Navigation Controls
  [Expand]Printing-Exporting
  [Expand]PDF Viewer
   Reporting
  [Expand]Snap
  [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]Reporting
[Expand]Report Server
[Expand]Dashboard
[Expand]eXpressApp Framework
[Expand]CodeRush
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Look And Feel Overview

The grid control, like other controls produced by DevExpress, supports Look And Feel technology. This technology enables you to provide a common appearance for all the controls in your application and then change the appearance of all controls at the same time. Note: here appearance is defined as the way in which buttons, borders, scroll bars, etc., are painted and the way in which they respond to user actions such as clicking, hovering the mouse pointer over them, etc. Generally, setting up a control's look and feel settings doesn't involve specifying the colors and fonts used to paint individual elements. For information on customizing these appearance aspects, please refer to the Appearances Overview, Custom Painting Basics and Alpha Blending and Background Images topics.

Expanded Customizing the Look And Feel Settings

You can choose one of the following scenarios to customize the grid control's look and feel:

  • Customize the grid control's look and feel settings.

    The grid control's look and feel settings can be accessed via the GridControl.LookAndFeel property of the UserLookAndFeel class. To ensure that this object's settings are in effect set its UserLookAndFeel.UseDefaultLookAndFeel property to false. Otherwise the grid will use the look and feel settings exposed by the Default LookAndFeel object.

  • Customize the look and feel settings of all the controls within the form (XtraForm or RibbonForm).

    When using the XtraForm or any its descendant it is easy to provide centralized management of the look and feel settings of all the controls residing within this form. Use the XtraForm.LookAndFeel property to customize these settings.

  • Customize the look and feel settings of all the controls within your application - via the Default LookAndFeel object.

    This approach can be used to provide centralized control over the look and feel settings of the controls in your applications. It implies accessing the UserLookAndFeel.Default static property at runtime or using the DefaultLookAndFeel component at design time.

For additional information on the Look And Feel mechanism and solutions for common tasks to do with customizing the look and feel of controls refer to the Look And Feel document.

 

Expanded Skins

The controls that support the Look And Feel mechanism also support Skins. Skins extend the standard set of painting schemes (Flat, UltraFlat, Style3D, WindowsXP and Office2003) introduced by the LookAndFeel objects. Unlike the other painting schemes skins are stored as bitmaps and the control just loads the required bitmaps from its resources when required.

Expanded Overriding Look And Feel Settings

Each View in the Grid Control is by default painted using the Look And Feel settings exposed by the grid control. It is possible to override these settings for a View by changing the View's BaseView.PaintStyleName property from "Default" to any of the other available names. See the BaseView.PaintStyleName topic for information on the available paint styles.

The editors displayed by a View inherit the View's look and feel settings by default. If you set the UserLookAndFeel.UseDefaultLookAndFeel property of the in-place editor's RepositoryItem.LookAndFeel object to false, the editor will be painted using its own look and feel settings while ignoring the look and feel settings exposed by its View.

Refer to the Look and Feel Inheritance topic for details on look and feel inheritance.

Expanded See Also

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