V4 : Please make DataContext the DataContext.

[xlsupport]

John,

while you're working on V4 could you please look at your current implementation of FlyleafHost's DataContext?

Remapping the actual DataContext to HostDataContext and replacing it with an instance of FlyleafHost is unconventional / unexpected / odd / ugly.

V4 will have other breaking changes. This is your chance ;-)

[SuRGeoNix]

I will be honest. I don't even remember :) But I do know that there is old code there which does not follow the current logic. This is also might need to be different if we are talking for attached/detached (hosted) vs stand-alone.

I currently stopped the development of v4 as I had a lot of design issues (this happens when you try to support everything - e.g. OS independent, complex packet-frame caches, multiple AVSD streams, filters etc.). That's also the reason that I'm back with v3 and really struggling to update this code (after 5+ years became too complex).

My upcoming updates will be the final recoding of the renderer -possible video decoder too- (it will resolve a lot of issues) and the next one is Controls/FlyleafHost. So, I will have those in mind when the time comes.

[xlsupport]

I'd love to help with the controls. That's the bit i know a bit about.

[SuRGeoNix]

Well mainly is win32 API, I'm even thinking to convert Surface' Window to just HwndHost. But generally, there are issues with Wpf and child windows. Does not like it. So might not work at all. I will let you know when the time comes and we see.

[coldays]

I did some testing today with HwndHost today.
It seems to do most of the work that FlyleafHost does today like positioning and resizing the surface and overlay windows.
I had to do one HwndHost for the surface and one HwndHost for the Overlay.
The drawbacks seems to be that it does not support clipping (which is also stated here https://learn.microsoft.com/en-us/dotnet/desktop/wpf/advanced/wpf-and-win32-interoperation#notable-differences-in-output-behavior)

[LazyCuteLion]

I think, Flyleaf should be a "control", just like "MediaElement",developer don't need to use like this code DataContext = new Player() and xaml set "Binding",the "Player"(Property) should be Flyleaf own's.

[LazyCuteLion]

@SuRGeoNix You don't need to care "MVVM",integrated into the interior will be better.
More think about: zero or less setting~