Microsoft UI XAML

The ColorPicker control suite consists of several specialized components designed for color selection. The primary control for application developers is ColorPicker.

Core Components:

• ColorPicker (Microsoft.UI.Xaml.Controls): The top-level control for user interaction.
• ColorPickerSlider (Microsoft.UI.Xaml.Controls.Primitives): A specialized 1D slider used within the ColorPicker template to represent HSV channels or Alpha. It features a gradient background corresponding to the color channel.
• ColorSpectrum (Microsoft.UI.Xaml.Controls.Primitives): A 2D graphic (Box or Ring shape) for selecting colors.
• SpectrumBrush (Microsoft.UI.Xaml.Controls.Primitives): A composition-based brush for rendering the spectrum background (requires Windows 1703/RS2 or later).

Helper Utilities:

• ColorHelpers: Specific to the ColorPicker controls.
• ColorConversion: Provides generalized RGB/HSV/Hex conversions and structures.

The XAML Compiler consists of several layers designed to transform XAML markup into compiled code and binary XBF files.

Core Components

• CompileXaml / xamlcompiler.exe: The outermost layer. CompileXaml is an MSBuild Task, while xamlcompiler.exe is a standalone executable. Both pass parameters to the shared inner layer.
• CompileXamlInternal: The shared inner layer and main entrypoint via CompileXamlInternal.DoExecute. It handles argument validation, type resolution (via Type Universe, Schema Context, and Type Resolver), XAML validation, code-behind generation, XAML rewriting, XBF generation (via genxbf.dll), and binding info generation.
• Type Resolution: Uses the Light Metadata Reader (LMR) to extract types from assemblies (dll and winmd). These objects are cached to optimize subsequent invocations.
• Xaml Dom Validation: The XamlDomValidator performs early checks on namespaces, elements, members, directives, and x:Bind usage. It acts as a first line of defense but is limited because it cannot inspect local types.
• Xaml Rewriting: The XamlConnectionIdRewriter modifies XAML before it reaches genxbf. It removes members like x:Name, Events, x:Bind, and x:DataType, and adds members like x:ConnectionId and x:Load="false" to preserve line/column information for debugging.

In System XAML, the application is responsible for manually running a message pump and draining the DispatcherQueue during shutdown to process asynchronous tasks scheduled during the WindowsXamlManager cleanup.

System XAML Shutdown Pattern:

1. Initialize Windows::UI::Xaml::WindowsXamlManager.
2. Run a standard GetMessage loop.
3. Call .Close() on the WindowsXamlManager instance.
4. Manually drain the DispatcherQueue using a PeekMessage loop to ensure all async work is processed.
5. Shut down the DispatcherQueueController if one was created.

WinUI 3 aims to improve this by requiring the app to provide the DispatcherQueue on the thread, avoiding the issues where XAML creates a DispatcherQueueController that it cannot correctly shut down.

// System XAML Shutdown Example

auto wxm = Windows::UI::Xaml::WindowsXamlManager::InitializeForCurrentThread();

// Run the message pump
MSG msg; 
while (GetMessage(&msg, nullptr, 0, 0)) 
{
    if (!CallPreTranslateMessageHelper()) 
    {
        TranslateMesasge(&msg); 
        DispatchMessage(&msg); 
    }
}

// Cleanup
wxm.Close();

// Drain the DispatcherQueue to process async work
while (PeekMessage(&msg, nullptr, 0, 0, PM_REMOVE)) { DispatchMessage(&msg); }

ShutdownDispatcherQueueController();

XAML rendering uses two distinct tree structures to build the final visual output:

1. CompNode Tree: An intermediate tree used to encapsulate the logic for setting up the Visual tree and mapping properties. A CUIElement generates a CompNode tree when it requires independent animations or specific composition features (see CUIElement::RequiresComposition() for details).
2. Visual Tree: The final tree of composition visuals used by the compositor to render the UI.

CompNode Types

• Tree Node (HWCompTreeNode and derived): Acts as the "spine" of the tree. It maps CUIElement properties to Visual properties using multiple Visuals. It can have child CompNodes.
• Content Node (HWCompLeafNode, HWCompRenderDataNode): Carries the Visuals that actually draw the content of a CUIElement and its subtree. Content nodes cannot have child CompNodes.

Standard CompNode Generation

When a CUIElement requires a CompNode, XAML typically generates three nodes:

1. TreeNode: Carries properties and serves as the parent for the ContentNode and child TreeNodes.
2. ContentNode: The first child of the TreeNode; carries the content of the element and its subtree.
3. Post-Subgraph Node: The next sibling of the TreeNode; carries content of the "right" subtree that draws higher in z-order.