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 Inheritance

General information on how the look and feel technology is supported by the grid control can be found in the Look And Feel Overview topic. That topic, however, only describes the grid control's default behavior. As there may be several Views involved in master-detail relationships, Views may either inherit look and feel settings from the grid control or provide their own settings. Additionally, each View uses in-place editors that can inherit look and feel settings from the View where they are displayed. Editors, like Views, can provide their own look and feel settings. This topic describes these look and feel inheritance aspects.

The following scheme represents the look and feel hierarchy implemented in the grid control.

Expanded Look And Feel Inheritance in Views

Initially each View's BaseView.PaintStyleName property is set to Default. This means that the View uses look and feel settings specified by the grid control's GridControl.LookAndFeel property. Thus, all Views have the same look and feel, and changing the grid control's look and feel settings affects all Views at once. Changing a View's BaseView.PaintStyleName property value applies the style specified to this View. Changing the grid control's look and feel settings will no longer affect these Views.

Note: the BaseView.PaintStyleName property provides more paint style variants than the look and feel settings. This is because the look and feel technology is common for all controls while the BaseView.PaintStyleName property value allows you to set grid control painting styles that may not be supported by other controls.

Expanded Look And Feel Inheritance Between Views And Inplace Editors

There are a number of properties controlling the look and feel of editors displayed within Views. The diagram below shows these properties and illustrates how look and feel settings are inherited.

The table below describes each property in detail.

Property Description
RepositoryItem.LookAndFeel This property provides look and feel settings for the entire editor. It exposes the UserLookAndFeel object that enables you to customize the editor's appearance as described in the Look And Feel and Skin Support topic. If that object's UserLookAndFeel.UseDefaultLookAndFeel property value is true, the editor uses settings provided by the parent View's BaseView.PaintStyleName property.
RepositoryItem.BorderStyle Specifies the paint style for the editor's border. If set to BorderStyles.Default, the border is painted as specified by the RepositoryItem.LookAndFeel property.
RepositoryItemButtonEdit.ButtonsStyle Specifies the paint style for the editor's buttons. If set to BorderStyles.Default, the buttons are painted as specified by the RepositoryItem.LookAndFeel property.
RepositoryItemPopupBase.PopupBorderStyle Specifies the paint style for the editor's popup window. If set to PopupBorderStyles.Default, the popup window's elements are painted as specified by the RepositoryItem.LookAndFeel property.

For additional information on using the RepositoryItem.BorderStyle, RepositoryItemButtonEdit.ButtonsStyle and RepositoryItemPopupBase.PopupBorderStyle properties, refer to the Border and Button Styles topic of the DevExpress Editors Library help system.

Expanded See Also

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