-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IWeakReferenceSource support #148
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stevenbrix I think I have most of the implementation but I'm blocked at this point. When I start going down the WeakReferenceSource creation, I don't have a COM object anymore and eventually I need it again for queryInterface implementations. I don't understand how it works in this codebase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice! does this change make it possible to add a public WeakReference<T: IWinRTObject>
so that we can keep WinRT weak references to objects?
@stevenbrix No, I think that implementation would look quite different, and likely much simpler. |
06b1d1a
to
26a9131
Compare
Implements
IWeakReferenceSource
on the COM interface that we synthesize for Swift objects sent to WinRT. This allows WinUI to keep weak references to our Swift objects. Also adds tests.