Replies: 5 comments
-
Concluding from the handle tree, it utilizes XAML Islands for interoperability of Win32 with UWP (+ WinUI2) Presumably the legacy Win32 drawing canvas has been put into a XAML Island, as it is both visually and functionally identical to the old one. |
Beta Was this translation helpful? Give feedback.
-
I would guess the drawing surface retains the Win32 code, and the Window and the rest of the UI is now in XAML. I am curious how the "ribbon" is being done. The flyouts are XAML but WinUI 2 or 3 doesn't yet have a Ribbon control, so is that also Win32 spawning Xaml flyouts? Or is there an Internal version of the Ribbon that may be released for everyone at some point, like the File Explorer team did with their CollectionView controls |
Beta Was this translation helpful? Give feedback.
-
I want to create a program that combines WinUI3 and Win32 hwnd. There is a technology called "Islands", but WinUI3 does not support "Islands" yet, so I am curious about how Microsoft does this, and the same goes for Notepad |
Beta Was this translation helpful? Give feedback.
-
The entire XAML part of the app is UWP + WinUI2, as indicated by the |
Beta Was this translation helpful? Give feedback.
-
So the drawing area is still a Win32 component? But the rest of it is WinUI 2. So the ribbon is not a skinned MFC one, and is in fact an internal CustomControl? |
Beta Was this translation helpful? Give feedback.
-
I want to implement paint tools similar to this, including windows for HWND and windows for XAML. How is this implemented?
Isn't this using Islands?
Beta Was this translation helpful? Give feedback.
All reactions