-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Export CachedWindow #12785
Export CachedWindow #12785
Conversation
This component is supposed to be internal to how bevy_winit works, it shouldn't be visible from the outside |
I agree. The problem I have is If you have an alternative idea, I'd be happy to implement it. One option would be to make the internal data of |
It seems your idea of "world swap" is not possible with private components handled by their own plugin... Does that mean that you'll have to open PRs on every plugin that your users will try to use with yours to make them public? |
It's only the window swapping part that requires access to private components. In general world swapping is expected to have minimal coupling between worlds. If users want to couple other parts, then they'd need to figure that out on a case-by-case basis. |
Closing due to won't fix conclusion from #12860. |
Objective
CachedWindow
resource. I am using this in bevy_worldswap when transferring newly-created windows to other worlds.Solution
CachedWindow
struct.Changelog
CachedWindow
is now public.