You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now View has internal var hWnd: HWND!. And If I want to make some extension, like DirectX rendering view, I can't integrate it with this frmaework. If make it public, I can create view and use it as target for DirectX rendering.
Any other changes, like adding new view subclasses, might also need access to hWnd if I need to make changes using native windows code.
The text was updated successfully, but these errors were encountered:
The hope is that there is enough of an API surface that we don't need to drop down to native Windows code to render the UI. Are there specific things that you were thinking of doing with DirectX that might be something that we could expose in a more structured manner?
Actually, atm I did switch to winui3, after I was unable to dynamicly update UI with this lib.
So now, nothing specific or structured needed for me.
But it was my problem when I just did initial test about rendering DirectX and some UI.
Right now
View
hasinternal var hWnd: HWND!
. And If I want to make some extension, like DirectX rendering view, I can't integrate it with this frmaework. If make it public, I can create view and use it as target for DirectX rendering.Any other changes, like adding new view subclasses, might also need access to
hWnd
if I need to make changes using native windows code.The text was updated successfully, but these errors were encountered: