mirror of
https://github.com/Stone-Red-Code/docs-desktop.git
synced 2026-09-07 16:06:07 +02:00
Replace various WPF include files with content (#1335)
* net-current-v30plus-md.md * net-current-v40plus-md.md * tla2sharptla-ui-md.md * tla2sharptla-uiautomation-md.md * tla2sharptla-winclient-md.md * tla2sharptla-xaml-md.md * tlasharptla-ui-md.md * tlasharptla-uiautomation-md.md * tlasharptla-winclient-md.md * tlasharptla-xaml-md.md * fix warnings
This commit is contained in:
@@ -11,7 +11,7 @@ ms.assetid: 08dd1606-02a2-4122-9351-c0afd2ec3a70
|
||||
---
|
||||
# Graphics Rendering Tiers
|
||||
|
||||
A rendering tier defines a level of graphics hardware capability and performance for a device that runs a [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] application.
|
||||
A rendering tier defines a level of graphics hardware capability and performance for a device that runs a WPF application.
|
||||
|
||||
<a name="graphics_hardware"></a>
|
||||
|
||||
@@ -31,7 +31,7 @@ A rendering tier defines a level of graphics hardware capability and performance
|
||||
|
||||
## Rendering Tier Definitions
|
||||
|
||||
The features of the graphics hardware determine the rendering capability of a [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] application. The [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] system defines three rendering tiers:
|
||||
The features of the graphics hardware determine the rendering capability of a WPF application. The WPF system defines three rendering tiers:
|
||||
|
||||
- **Rendering Tier 0** No graphics hardware acceleration. All graphics features use software acceleration. The DirectX version level is less than version 9.0.
|
||||
|
||||
@@ -50,7 +50,7 @@ A rendering tier defines a level of graphics hardware capability and performance
|
||||
> [!NOTE]
|
||||
> Starting in the .NET Framework 4, rendering tier 1 has been redefined to only include graphics hardware that supports DirectX 9.0 or greater. Graphics hardware that supports DirectX 7 or 8 is now defined as rendering tier 0.
|
||||
|
||||
A rendering tier value of 1 or 2 means that most of the graphics features of [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] will use hardware acceleration if the necessary system resources are available and have not been exhausted. This corresponds to a DirectX version that is greater than or equal to 9.0.
|
||||
A rendering tier value of 1 or 2 means that most of the graphics features of WPF will use hardware acceleration if the necessary system resources are available and have not been exhausted. This corresponds to a DirectX version that is greater than or equal to 9.0.
|
||||
|
||||
The following table shows the differences in graphics hardware requirements for rendering tier 1 and rendering tier 2:
|
||||
|
||||
@@ -68,10 +68,10 @@ A rendering tier defines a level of graphics hardware capability and performance
|
||||
|-------------|-----------|
|
||||
|2D rendering|Most 2D rendering is supported.|
|
||||
|3D rasterization|Most 3D rasterization is supported.|
|
||||
|3D anisotropic filtering|[!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] attempts to use anisotropic filtering when rendering 3D content. Anisotropic filtering refers to enhancing the image quality of textures on surfaces that are far away and steeply angled with respect to the camera.|
|
||||
|3D MIP mapping|[!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] attempts to use MIP mapping when rendering 3D content. MIP mapping improves the quality of texture rendering when a texture occupies a smaller field of view in a <xref:System.Windows.Controls.Viewport3D>.|
|
||||
|3D anisotropic filtering|WPF attempts to use anisotropic filtering when rendering 3D content. Anisotropic filtering refers to enhancing the image quality of textures on surfaces that are far away and steeply angled with respect to the camera.|
|
||||
|3D MIP mapping|WPF attempts to use MIP mapping when rendering 3D content. MIP mapping improves the quality of texture rendering when a texture occupies a smaller field of view in a <xref:System.Windows.Controls.Viewport3D>.|
|
||||
|Radial gradients|While supported, avoid the use of <xref:System.Windows.Media.RadialGradientBrush> on large objects.|
|
||||
|3D lighting calculations|[!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] performs per-vertex lighting, which means that a light intensity must be calculated at each vertex for each material applied to a mesh.|
|
||||
|3D lighting calculations|WPF performs per-vertex lighting, which means that a light intensity must be calculated at each vertex for each material applied to a mesh.|
|
||||
|Text rendering|Subpixel font rendering uses available pixel shaders on the graphics hardware.|
|
||||
|
||||
The following features and capabilities are hardware accelerated only for rendering tier 2:
|
||||
@@ -84,40 +84,40 @@ A rendering tier defines a level of graphics hardware capability and performance
|
||||
|
||||
|Feature|Notes|
|
||||
|-------------|-----------|
|
||||
|Printed content|All printed content is rendered using the [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] software pipeline.|
|
||||
|Printed content|All printed content is rendered using the WPF software pipeline.|
|
||||
|Rasterized content that uses <xref:System.Windows.Media.Imaging.RenderTargetBitmap>|Any content rendered by using the <xref:System.Windows.Media.Imaging.RenderTargetBitmap.Render%2A> method of <xref:System.Windows.Media.Imaging.RenderTargetBitmap>.|
|
||||
|Tiled content that uses <xref:System.Windows.Media.TileBrush>|Any tiled content in which the <xref:System.Windows.Media.TileBrush.TileMode%2A> property of the <xref:System.Windows.Media.TileBrush> is set to <xref:System.Windows.Media.TileMode.Tile>.|
|
||||
|Surfaces that exceed the maximum texture size of the graphics hardware|For most graphics hardware, large surfaces are 2048x2048 or 4096x4096 pixels in size.|
|
||||
|Any operation whose video RAM requirement exceeds the memory of the graphics hardware|You can monitor application video RAM usage by using the Perforator tool that is included in the [WPF Performance Suite](/previous-versions/dotnet/netframework-4.0/aa969767(v=vs.100)) in the Windows SDK.|
|
||||
|Layered windows|Layered windows allow [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] applications to render content to the screen in a non-rectangular window. On operating systems that support Windows Display Driver Model (WDDM), such as Windows Vista and Windows 7, layered windows are hardware accelerated. On other systems, such as Windows XP, layered windows are rendered by software with no hardware acceleration.<br /><br /> You can enable layered windows in [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] by setting the following <xref:System.Windows.Window> properties:<br /><br /> - <xref:System.Windows.Window.WindowStyle%2A> = <xref:System.Windows.WindowStyle.None><br />- <xref:System.Windows.Window.AllowsTransparency%2A> = `true`<br />- <xref:System.Windows.Controls.Control.Background%2A> = <xref:System.Windows.Media.Brushes.Transparent%2A>|
|
||||
|Layered windows|Layered windows allow WPF applications to render content to the screen in a non-rectangular window. On operating systems that support Windows Display Driver Model (WDDM), such as Windows Vista and Windows 7, layered windows are hardware accelerated. On other systems, such as Windows XP, layered windows are rendered by software with no hardware acceleration.<br /><br /> You can enable layered windows in WPF by setting the following <xref:System.Windows.Window> properties:<br /><br /> - <xref:System.Windows.Window.WindowStyle%2A> = <xref:System.Windows.WindowStyle.None><br />- <xref:System.Windows.Window.AllowsTransparency%2A> = `true`<br />- <xref:System.Windows.Controls.Control.Background%2A> = <xref:System.Windows.Media.Brushes.Transparent%2A>|
|
||||
|
||||
<a name="other_resources"></a>
|
||||
|
||||
## Other Resources
|
||||
|
||||
The following resources can help you analyze the performance characteristics of your [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] application.
|
||||
The following resources can help you analyze the performance characteristics of your WPF application.
|
||||
|
||||
### Graphics Rendering Registry Settings
|
||||
|
||||
[!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] provides four registry settings for controlling [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] rendering:
|
||||
WPF provides four registry settings for controlling WPF rendering:
|
||||
|
||||
|Setting|Description|
|
||||
|-------------|-----------------|
|
||||
|**Disable Hardware Acceleration Option**|Specifies whether hardware acceleration should be enabled.|
|
||||
|**Maximum Multisample Value**|Specifies the degree of multisampling for antialiasing 3D content.|
|
||||
|**Required Video Driver Date Setting**|Specifies whether the system disables hardware acceleration for drivers released before November 2004.|
|
||||
|**Use Reference Rasterizer Option**|Specifies whether [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] should use the reference rasterizer.|
|
||||
|**Use Reference Rasterizer Option**|Specifies whether WPF should use the reference rasterizer.|
|
||||
|
||||
These settings can be accessed by any external configuration utility that knows how to reference the [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] registry settings. These settings can also be created or modified by accessing the values directly by using the Windows Registry Editor. For more information, see [Graphics Rendering Registry Settings](../graphics-multimedia/graphics-rendering-registry-settings.md).
|
||||
These settings can be accessed by any external configuration utility that knows how to reference the WPF registry settings. These settings can also be created or modified by accessing the values directly by using the Windows Registry Editor. For more information, see [Graphics Rendering Registry Settings](../graphics-multimedia/graphics-rendering-registry-settings.md).
|
||||
|
||||
### WPF Performance Profiling Tools
|
||||
|
||||
[!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] provides a suite of performance profiling tools that allow you to analyze the run-time behavior of your application and determine the types of performance optimizations you can apply. The following table lists the performance profiling tools that are included in the Windows SDK tool, WPF Performance Suite:
|
||||
WPF provides a suite of performance profiling tools that allow you to analyze the run-time behavior of your application and determine the types of performance optimizations you can apply. The following table lists the performance profiling tools that are included in the Windows SDK tool, WPF Performance Suite:
|
||||
|
||||
|Tool|Description|
|
||||
|----------|-----------------|
|
||||
|Perforator|Use for analyzing rendering behavior.|
|
||||
|Visual Profiler|Use for profiling the use of [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] services, such as layout and event handling, by elements in the visual tree.|
|
||||
|Visual Profiler|Use for profiling the use of WPF services, such as layout and event handling, by elements in the visual tree.|
|
||||
|
||||
The WPF Performance Suite provides a rich, graphical view of performance data. For more information about WPF performance tools, see [WPF Performance Suite](/previous-versions/dotnet/netframework-4.0/aa969767(v=vs.100)).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user