![]() A SwapChainPanel can be any size, using standard XAML Height and Width properties.Similar to the z-order improvements this enabled for WebView, leveraging DirectComposition as a high performance system compositor ensured we could lift many of the restrictions required by the SwapChainBackgroundPanel control: The framework then uses DirectComposition to directly compose together all the different types of content you may have in your app, such as DirectX, HTML, media, and XAML. ![]() The SwapChainPanel control makes it easier to include 2D and 3D DirectX content within the rest of a XAML app’s UI and render it at 60 FPS: you can now create a DirectX IDXGISwapChain and associate it with a SwapChainPanel control anywhere in the XAML visual tree. Multi-threaded rendering and Direct2D batching: these new options can help improve your app’s performance when drawing DirectX content to SurfaceImageSource and VirtualSurfaceImageSource surfaces. ![]() The SwapChainPanel control: this control builds upon the functionality of SwapChainBackgroundPanel to provide a great deal more flexibility in rendering, layout, and responding to input.I’m therefore excited to talk about some of the new functionality we’ve introduced in Windows 8.1: Since the launch of Windows 8, we’ve heard feedback from developers that you wanted the ability to do the same sort of entirely custom 60 FPS DirectX rendering where the app fully controls the swap chain and presentation timing to the screen, but without the layout restrictions imposed by SwapChainBackgroundPanel or the UI thread synchronization required for SurfaceImageSource. ![]() While the SwapChainBackgroundPanel control provided a high-performance rendering solution that made it ideal for DirectX-focused apps like games, it has a number of restrictions: there can be only one active at a time, it always fills the full window, and it has to be at the root of the XAML page layout. ![]()
0 Comments
Leave a Reply. |