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
{{ message }}
Repository navigation
Feature Request: When the app sets a custom winrt_activation_handler, please provide an easy way to call the default cppwinrt "get activation handler" logic #1567
I'd like to be able to write a custom winrt_activation_handler handler that recognizes specific types, that works great. But I'd also like to be able to call into the default logic in the case I don't recognize the type, hit an error, etc.
I suspect what Jesse Collins (@JesseCol) is looking for is something like get_runtime_activation_factory_impl_but_ignore_winrt_activation_handler or a way to indicate that the call to winrt_activation_handler should not be the end of the hunt. CsWinRT's implementation makes it a bit easier since you can return null and have it continue on its normal activation hunt sequence.
Activity
sylveon commentedon Apr 14, 2026
https://learn.microsoft.com/en-us/windows/win32/api/roapi/nf-roapi-rogetactivationfactory
JohnMcPMS commentedon May 19, 2026
I suspect what Jesse Collins (@JesseCol) is looking for is something like
get_runtime_activation_factory_impl_but_ignore_winrt_activation_handleror a way to indicate that the call towinrt_activation_handlershould not be the end of the hunt. CsWinRT's implementation makes it a bit easier since you can return null and have it continue on its normal activation hunt sequence.YexuanXiao commentedon Sep 9, 2026
Before setting a new handler, you can store the old handler in a global variable, and then call the old handler from within the new handler.
sylveon commentedon Sep 9, 2026
I believe they want access to the rest of this function:
which can't be achieved by just storing an existing handler.