HO-COOH

@DarranRowe Now things get interesting. I tried separated out the `WindowEx` class into a winrt component project and things indeed worked. You can reproduce my issue if you don't separate...

This is still an issue today, and I am still not able to inherit a custom Window (defined within in the same project) and have to rewrite quite a lot...

Just tested, this exact issue does NOT happen with C#. Any hope of this getting fixed so I don't have to duplicate tons of code?

[The workaround I compose](https://github.com/HO-COOH/WinUIEssentials?tab=readme-ov-file#autosuggestboxhelper)

Do not even try to rename an idl file after it is created. All the internal file references will go wrong. Rename the idl when you create it, not after.

It seems like `UISettings.ColorValueChanged` is not called on Windows 10 (at least for 19045) with Winui3 1.4.2. [Repro here](https://github.com/HO-COOH/WinUI-Bug)

> Any word on when this might be fixed, or if there's a known viable workaround? [There is](https://github.com/CommunityToolkit/Windows/pull/445), but somehow still not getting reviewed

@ghost1372 That would be nice. But as a C++ dev myself, I would hope for a C++ version.

The error handling logic is already quite messy, and all this leaking issue can be trivially fixed by simply replacing all the raw COM pointers with a smart pointer `ComPtr`...

> since there is no way to query that the window is in a state where it's closed Isn't there a `Window.Closed` [event](https://learn.microsoft.com/en-us/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.window.closed?view=windows-app-sdk-1.5#microsoft-ui-xaml-window-closed) which you can handle?