Does bgfx support winui3?

[tetrisplusplus]

Does bgfx support winui3?

I'm having trouble figuring out how to do bgfx::init with SwapChainPanel.

When I link bgfx as native static library, the BX_PLATFORM_WINRT macro is not enabled.

According to the site below, the Windows App SDK code seems to belong to WINAPI_FAMILY_DESKTOP_APP.
https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/migrate-to-windows-app-sdk/misc-info

If bgfx does not support it, is there any plan to support it in the future?

[bkaradzic]

Over years I supported different WinRT / WinPhone / etc. targets. MS is changing API so much that it's not worth supporting... It's mostly dead platform that no one cares about, and they messing with APIs non-stop.

So I don't really know how to answer your question, I don't know what winui3 is, how is related to WinRT that was supported before, etc.

[tetrisplusplus]

I did some research on WinUI3.

WinUI3 is UI library in the Windows App SDK.
https://learn.microsoft.com/en-us/windows/apps/winui/winui3/

WinUI 3 is the native UI platform component that ships with the Windows App SDK (completely decoupled from Windows SDKs). The Windows App SDK provides a unified set of APIs and tools that can be used to create production desktop apps that target Windows 10 and later, and can be published to the Microsoft Store.

The Windos App SDK was called Project Reunion.
https://mspoweruser.com/microsoft-explains-project-reunion/

Project Reunion, a new project to make app development easier for Windows 10 platform. Project Reunion unifies access to existing Win32 (legacy Windows API) and UWP (Universal Windows Platform) APIs and makes them available decoupled from the OS, via tools like NuGet. Apps built using Project Reunion components can work across all the Windows 10 versions and devices.

In Windows App SDK, the root namespace has been changed to Microsoft.
For example, Windows.UI.Xaml is to Microsoft.UI.Xaml.

In WinUI3 (Windows App SDK), there are packaged and unpackaged applications.
The former is a store app (like uwp app) and the latter is a desktop app (win32 app).

The packaged and unpackaged apps switch depending on whether the following is specified or not.
WINAPI_FAMILY is also changed from WINAPI_FAMILY_PC_APP to WINAPI_FAMILY_DESKTOP_APP by adding the following to vcxproj

<WindowsPackageType>None</WindowsPackageType>

https://learn.microsoft.com/en-us/windows/apps/winui/winui3/create-your-first-winui3-app#unpackaged-create-a-new-project-for-an-unpackaged-c-or-c-winui-3-desktop-app

I don't know about the relationship between WinUI3 and the past WinRT.
I am interested in creating a modern UI desktop(win32) application based on xaml.
In other words, I want to use SwapChainPanel instead of HWND as the rendering destination for desktop (win32) applications.

[tetrisplusplus]

Next, I experimented with initializing bgfx in an unpackaged WinUI3 application.

By modifying Platform.h, I forced BX_PLATFORM_WINRT to be enabled.

The result failed with the following line
dxgi.cpp L.153

*hr = swapChainPanelNative->SetSwapChain(swapChain);

It seems that updating the SwapChainPanel can be done outside of the UI thread (Main thread), but its initialization (SetSwapChain) must be done in the UI thread.
https://learn.microsoft.com/en-us/windows/win32/api/windows.ui.xaml.media.dxinterop/nf-windows-ui-xaml-media-dxinterop-iswapchainpanelnative-setswapchain

This method has to be called on the UI thread the parent SwapChainPanel belongs to. If called on another thread, it will return 0x8001010E (RPC_E_WRONG_THREAD, "The application called an interface that was marshaled for a different thread").

I don't know how to avoid this failure.

It might be nice to have an override option based on user responsibility as to which Platform Macro to enable.