#Macpass window associations full#

(The IDXGIOutput can be retrieved from IDXGISwapChain::GetContainingOutput. If a matching mode is found, allow the resize. If the application further chooses to restrict its window's client area to just those that match supported full-screen resolutions, the application can field WM_SIZING, then check against IDXGIOutput::FindClosestMatchingMode. A fully flexible application would make no such restriction, but UI elements or other design considerations can, of course, make this flexibility untenable.

While windowed, the application can, if it chooses, restrict the size of its window's client area to sizes to which it is comfortable rendering. Thus, a call to ResizeBuffers on WM_SIZE is always recommended, since WM_SIZE is always sent during a fullscreen transition.

Even if a stretch is not required, presentation may not be optimal because the back buffers might not be directly interchangeable with the front buffer. If the application does not perform this sequence, DXGI will still make the full-screen/windowed transition, but may be forced to use a stretch operation (since the back buffers may not be the correct size), which may be less efficient. This gives the swap chain(s) an opportunity to resize the back buffers, and/or recreate them to enable full-screen flipping operation. For example, on a WM_SIZE message, the application should release any outstanding swap-chain back buffers, call IDXGISwapChain::ResizeBuffers, then re-acquire the back buffers from the swap chain(s).

#Macpass window associations full#

If the application switches to full-screen mode, DXGI will choose a full-screen resolution to be the smallest supported resolution that is larger or the same size as the current back buffer size.Īpplications can make some changes to make the transition from windowed to full screen more efficient. The combination of WindowHandle and Flags informs DXGI to stop monitoring window messages for the previously-associated window.